Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Apr 09, 2020 at 12:58:48PM -0700, Linus Torvalds wrote:
> On Thu, Apr 9, 2020 at 12:56 PM Matthew Wilcox <willy@xxxxxxxxxxxxx> wrote:
> >
> > We should probably give Stephen a cc here ...
> 
> Heh. I already did, but then that got broken because Andrew had lost
> that part of the thread and the discussion re-started.
> 
> So Stephen was already cc'd for my original request to have linux-next
> kick things out aggressively.
> 

Well, if (for example) we look at
"linux-next test error: WARNING: suspicious RCU usage in ovs_ct_exit"
(https://lkml.kernel.org/lkml/000000000000e642a905a0cbee6e@xxxxxxxxxx/),
it was sent to the maintainers of net/openvswitch/ where the warning occurred.
It was then ignored.

Would it help if bugs blocking testing on linux-next were Cc'ed to
linux-next@xxxxxxxxxxxxxxx, so that Stephen could investigate?

FWIW, the issue of "syzbot report sent and ignored for months/years" is actually
a much broader one which applies to all bugs, not just build / test breakages.
There are tons of open bugs on https://syzkaller.appspot.com/upstream which are
definitely still valid (sort by "Last" occurred).  Long-term, to fix this we
really need syzbot to start sending reminders.  But first there's work needed to
make the noise level low enough so that people don't just tune them out.

- Eric




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux