On Thu, Apr 9, 2020 at 2:49 AM Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > On Tue, 7 Apr 2020 21:40:08 -0400 Peter Xu <peterx@xxxxxxxxxx> wrote: > > > The two patches should fix below syzbot reports: > > > > BUG: unable to handle kernel paging request in kernel_get_mempolicy > > https://lore.kernel.org/lkml/0000000000002b25f105a2a3434d@xxxxxxxxxx/ > > > > WARNING: bad unlock balance in __get_user_pages_remote > > https://lore.kernel.org/lkml/00000000000005c65d05a2b90e70@xxxxxxxxxx/ > > (Is there an email address for the syzbot operators?) > > sysbot does test linux-next, yet these patches sat in linux-next for a > month without a peep, but all hell broke loose when they hit Linus's > tree. How could this have happened? The same thing: https://groups.google.com/d/msg/syzkaller-bugs/phowYdNXHck/qU1P0TsjBAAJ linux-next is boot-broken for more than a month and bugs are piling onto bugs, I've seen at least 3 different ones. syzbot can't get any working linux-next build for testing for a very long time now.
