Project

General

Profile

Actions
Copy link

Feature #6955

closed

Feature #6880: Investigate what dependent modules should be analysed together to find well known bugs

Example of target bug that can not be found without multi-module analysis

Added by Evgeny Novikov about 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
High
Assignee:
Alexey Polushkin
Category:
Program fragments generation
Target version:
-
Start date:
03/10/2016
Due date:
% Done:

0%

Estimated time:
Published in build:

Description

The target bug is in __w1_remove_master_device() that is called when all devices added by means of w1_add_master_device() are deregistered. But w1_add_master_device() is called just from other modules.

This issue was initially investigated by Pavel.

Actions
Copy link
 #1

Updated by Alexey Polushkin almost 8 years ago

The module 'drivers/w1/wire.ko' requires 'drivers/w1/masters/ds2482.ko' or 'drivers/w1/masters/ds1wm.ko' module. Scotch strategy ('cluster size' >= 2) creates group for every required module. Advanced strategy ('cluster size' >= 2) only for 'drivers/w1/masters/ds1wm.ko' creates group, when using default parameters. But with option 'minimize groups for module' = False, creates groups for both modules.

Actions
Copy link
 #2

Updated by Evgeny Novikov almost 8 years ago

  • Status changed from New to Closed

For me it is enough.

Actions
Copy link

Also available in: Atom PDF