| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Make it possible to print more debugging information when (re)generating
a subsystem list.
Include parent inference details to the source code itself and add a
-debug flag to list the source files assigned to each subsystem.
|
| |
|
|
|
|
|
|
|
| |
There was a mistake in the Linux subsystem generation rules that led to
the exclusion of exfat-related syz_mount_image calls from the resulting
subsystem descriptions.
Verify the rules before applying them. Fix other problems found by the
check.
|
| |
|
|
| |
It will help keep more generic reports in "net".
|
| |
|
|
|
| |
If a record was specified in a custom subsystem list, do not consider it
while grouping records by mailing list.
|
| |
|
|
|
|
|
| |
There are cases when a subsystem doesn't have a mailing list and yet
we'd prefer not to merge it with others. Let's add the ability to add
custom rules that join several specified MAINTAINERS records into one
Subsystem.
|
| |
|
|
|
|
| |
Remove the entity and match subpackages.
Regenerate the linux.go file.
|
| |
|
|
| |
And regenerate the Linux rules file.
|
| |
|
|
|
|
|
|
|
| |
For that, extract a coincidence count matrix from a path coverage, then
apply the following rule.
Subsystem A is a child of B if both hold true:
1) More than 2/3 of paths that relate to A also relate to B.
2) B covers more directory tree entities than A.
|
| |
|
|
| |
Otherwise we can get too many mailing lists at the same time.
|
| |
|
|
|
| |
Now that we have subsystem names, it's easy to test whether syzkaller
extract and groups the path matching rules correctly.
|
| |
|
|
| |
This information will let us extract subsystems from reproducers.
|
| |
|
|
|
|
|
|
|
| |
Extract the short subsystem name from the mailing list email.
Stip the common prefixes and suffixes and make sure there are no
duplicates.
As a fallback, assign the whole list email address as a subsystem name.
|
| |
|
