| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Remove the entity and match subpackages.
Regenerate the linux.go file.
|
| |
|
|
| |
This lets us reduce the amount of code in parents.go.
|
| |
|
|
|
|
|
|
| |
In the previous steps we eliminate some of the extracted subsystems. It
helps to have fewer contention while assigning the names.
As a result, we need to only rely on emails during parents
trasnformations.
|
| |
|
|
| |
And regenerate the Linux rules file.
|
| |
|
|
|
|
| |
linux-security-module is too long, we could use just lsm.
Also, overlayfs had a different name, therefore we cannot infer it from
the mailing list as is.
|
| |
|
|
| |
Simplify the code by removing the unnecessary itermediate structures.
|
| |
|
|
|
|
| |
Despite the automatic logic we already have, there are still a few
emails that slip the check. For now let's keep them in a separate array,
maybe later we'll figure out a pattern.
|
| |
|
|
|
| |
This list was generated using an older version of the code. It'll serve
as a baseline for further changes.
|
| |
|
|
|
| |
Instead of just assigning parents, also remove small and highly
overlapping subsystems.
|
| |
|
|
|
| |
We don't really care about Documentation/ and similar folders. Exclude
such path matching rules after parsing MAINTAINERS.
|
| |
|
|
|
|
|
|
| |
For now, let's use a straightforward approach:
1) Extract all subsystems for each guilty path and syz reproducer.
2) If there are both parents and children in the list, remove parents.
3) Count the remaining subsystems.
4) Pick the ones that appear most often.
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Take care of the corner cases and add extensive tests.
|
| |
|
