diff options
| author | Alexander Potapenko <glider@google.com> | 2023-08-04 14:22:59 +0200 |
|---|---|---|
| committer | Aleksandr Nogikh <nogikh@google.com> | 2023-08-31 14:06:44 +0000 |
| commit | 696ea0d2f4fdaa17db929e152edba19bf7666d84 (patch) | |
| tree | 807a2800dd3f1d7d0844f431273fb9d21ab7bf0e /dashboard/dashapi | |
| parent | 4ad3538b47648c656a279e97acb851dbbdf70129 (diff) | |
pkg/report: drop "ALT: KMSAN origin" titles for uninit reports
It was initially proposed in
https://github.com/google/syzkaller/issues/1575 that KMSAN reports with
the same origin should be clustered together using an alt title.
This however turns out to be too aggressive: certain KMSAN reports have
their uninitialized values originating from common functions - this
leads to too many KMSAN reports being glued together. Because KMSAN
reports can be also clustered with KASAN reports or other kernel panics,
ultimately seemingly unrelated crashes are considered similar just
because they share their top frames with two KMSAN reports that, in
turn, share the same origin.
The resulting issues on the dashboard look confusing to the users, they
are hard to find and require manual untangling, which probably outweighs
the benefits of having KMSAN issues with exactly the same origin
clustered together.
For other types of KMSAN reports (infoleaks and use-after-frees) the alt
titles are preserved. First, there are fewer of those on the dashboard.
Second, they are rarely grouped together with non-KASAN reports and
are less likely to cause a lot of mess.
Diffstat (limited to 'dashboard/dashapi')
0 files changed, 0 insertions, 0 deletions
