Feature #7661
closedSupport generation of verification objects for modules compiled in kernel
0%
Description
Now we support generation of verification objects just for modules compiled and linked as *.ko files. But it seems that for us it shouldn't matter because of eventually we work with subsets of C files with corresponding compiler options.
Maybe it will be quite easy to generate verification objects if the user will specify exact paths to modules, e.g. drivers/usb/core/usbcore.o, but this also should be done for "modules" in subdirectories and even for all "modules". So some methods to distinguish objects that constitute modules should be used.
Updated by Alexey Polushkin over 7 years ago
- Status changed from New to Resolved
Implemented in 'modules_path_o' branch
Updated by Evgeny Novikov over 7 years ago
- Status changed from Resolved to Open
I would like to ask you to carefully test this new approach before merging its implementation to master. Please, run various tests and the validation set (just some subsets are enough). In particular it is interesting will it work with external modules.
Updated by Alexey Polushkin over 7 years ago
- Status changed from Open to Resolved
This have been tested in 'Testing rule specifications' (42 external module), and 'Validation on commits in Linux kernel Git repositories' (4 task) tests.
Updated by Evgeny Novikov over 7 years ago
- Status changed from Resolved to Closed
I merged the given branch to master in faaa788. The only thing to do is to compare differences in generated verification objects but I don't think that this will hurt us much.