On Wed, Apr 08, 2020 at 05:47:32PM -0700, Andrew Morton 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?) I'd suggest syzkaller-bugs@xxxxxxxxxxxxxxxx (added to the Cc). But there's a deeper problem in that we don't have anywhere to stash that kind of information in the kernel tree right now. Perhaps a special entry in the MAINTAINERS file for bot operators? Or one entry per bot? > 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? > > Possibly I've been carrying a later patch which fixed all this up, but > I'm not seeing anything like that. Nothing at all against mm/gup.c. > >
