kmod/testsuite/module-playground
Yauheni Kaliuta 9be03c52cc testsuite: depmod: check netsted loops reporting
The patch adds nested loops configuration for the loop test:

mod-loop-h -> mod-loop-i -> mod-loop-j -> mod-loop-k
   ^                           |               |
    ---------------------------                |
   |                                           |
    -------------------------------------------

making 2 loops with common edges:

mod-loop-h -> mod-loop-i -> mod-loop-j -> mod-loop-h
mod-loop-h -> mod-loop-i -> mod-loop-j -> mod-loop-k -> mod-loop-h

The actual output for the loops is:

depmod: ERROR: Cycle detected: mod_loop_h -> mod_loop_h
depmod: ERROR: Cycle detected: mod_loop_i -> mod_loop_j -> mod_loop_k -> mod_loop_h -> mod_loop_i

(the order in the second doesn't matter, but the first one is
incorrect)

Signed-off-by: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
2017-02-22 04:50:22 -08:00
..
cache testsuite: depmod: check netsted loops reporting 2017-02-22 04:50:22 -08:00
.gitignore build: cache modules from playground 2015-05-31 15:38:47 -03:00
dummy.sha1 testsuite: port signature-check modules to module-playground 2015-02-21 15:51:42 -02:00
dummy.sha256 testsuite: port signature-check modules to module-playground 2015-02-21 15:51:42 -02:00
Makefile testsuite: depmod: check netsted loops reporting 2017-02-22 04:50:22 -08:00
Makefile.arch module-playground: allow to cross-compile modules 2015-02-21 11:40:27 -02:00
mod-fake-cciss.c testsuite: port modules-order-compressed to module-playground 2015-02-19 19:50:16 -02:00
mod-fake-hpsa.c testsuite: port modules-order-compressed to module-playground 2015-02-19 19:50:16 -02:00
mod-fake-scsi-mod.c testsuite: port modules-order-compressed to module-playground 2015-02-19 19:50:16 -02:00
mod-foo-a.c testsuite: port test-dependencies to module-playground 2015-02-03 01:12:13 -02:00
mod-foo-b.c testsuite: port test-dependencies to module-playground 2015-02-03 01:12:13 -02:00
mod-foo-c.c testsuite: port test-dependencies to module-playground 2015-02-03 01:12:13 -02:00
mod-foo.c testsuite: port test-dependencies to module-playground 2015-02-03 01:12:13 -02:00
mod-loop-a.c testsuite: depmod: add module dependency outside cyclic chain 2016-11-08 22:28:40 -02:00
mod-loop-b.c testsuite: depmod: add module dependency outside cyclic chain 2016-11-08 22:28:40 -02:00
mod-loop-c.c testsuite: port detect-loop test to module-playground 2015-02-09 14:07:31 -02:00
mod-loop-d.c testsuite: port detect-loop test to module-playground 2015-02-09 14:07:31 -02:00
mod-loop-e.c testsuite: port detect-loop test to module-playground 2015-02-09 14:07:31 -02:00
mod-loop-f.c testsuite: depmod: add module dependency outside cyclic chain 2016-11-08 22:28:40 -02:00
mod-loop-g.c testsuite: depmod: add module dependency outside cyclic chain 2016-11-08 22:28:40 -02:00
mod-loop-h.c testsuite: depmod: check netsted loops reporting 2017-02-22 04:50:22 -08:00
mod-loop-i.c testsuite: depmod: check netsted loops reporting 2017-02-22 04:50:22 -08:00
mod-loop-j.c testsuite: depmod: check netsted loops reporting 2017-02-22 04:50:22 -08:00
mod-loop-k.c testsuite: depmod: check netsted loops reporting 2017-02-22 04:50:22 -08:00
mod-loop.h testsuite: depmod: check netsted loops reporting 2017-02-22 04:50:22 -08:00
mod-simple-i386.ko testsuite: leave arch-specific modules in tree 2015-02-21 15:05:25 -02:00
mod-simple-sparc64.ko testsuite: leave arch-specific modules in tree 2015-02-21 15:05:25 -02:00
mod-simple-x86_64.ko testsuite: leave arch-specific modules in tree 2015-02-21 15:05:25 -02:00
mod-simple.c testsuite: beef up module-playground in the build system 2015-02-03 01:09:17 -02:00
README testsuite: leave arch-specific modules in tree 2015-02-21 15:05:25 -02:00

Pre-compiled modules
====================

Some modules are pre-compiled due to needing cross-compilers present on the
build/dev machine which is inconvenient. Makefile is ready to compile them again
in case they are missing:

1) Prepare the linux kernel trees to build external modules, i.e.:

   kernel $ make ARCH=<arch> CROSS_COMPILER=<cross-compiler-prefix> defconfig
   kernel $ make ARCH=<arch> CROSS_COMPILER=<cross-compiler-prefix> modules_prepare

   For each architecture. See the Makefile to check which are the supported architectures.

2) Export the variables below to point to the right place:

   KDIR_<arch>:                for each architecture it needs to point to a
                               kernel tree configured as in (1)

   CROSS_COMPILER_<arch:       for each architecture it needs to point to the
			       correct toolchain prefix. Leave it blank if a
			       cross-compiler is not needed (example: you are
			       building a 32b module with a multilib compiler).


3) Remove every %-<arch>.ko. After this the build system will recreate them.