lkml.org 
[lkml]   [2022]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectAuto-invalidating old syzbot reports?
Currently the upstream Linux kernel has 888 open syzbot reports
(https://syzkaller.appspot.com/upstream). However, nearly two-thirds of them
(577) were reported more than 1 year ago. Old reports are often for bugs that
were already fixed. They can also be reports that got overlooked, forgotten
about, not sent to the right place, etc. Kernel maintainers also change over
time, so the current maintainer(s) might never have received the original report
even if syzbot sent the original report to the correct maintainer(s).

Having these old reports open is preventing syzbot from re-reporting any bugs
with the same crash signature (where a crash signature is something like
"KASAN: null-ptr-deref Read in percpu_ref_exit") if it is still being seen.

syzbot does auto-invalidate some old bugs, but only ones without a reproducer.

Given that humans aren't keeping up with these reports, has it been considered
to auto-invalidate all old syzbot reports -- not just ones without a reproducer?

- Eric

\
 
 \ /
  Last update: 2022-06-07 00:23    [W:0.132 / U:0.508 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site