[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACT4Y+bhQVcpSkSh_OZ5ZanfFZUqn2iypLhG_Z-nWKTkaYr1jw@mail.gmail.com>
Date: Thu, 9 Apr 2020 14:55:42 +0200
From: Dmitry Vyukov <dvyukov@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Peter Xu <peterx@...hat.com>, LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux-MM <linux-mm@...ck.org>
Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports
On Thu, Apr 9, 2020 at 2:49 AM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> On Tue, 7 Apr 2020 21:40:08 -0400 Peter Xu <peterx@...hat.com> 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@google.com/
> >
> > WARNING: bad unlock balance in __get_user_pages_remote
> > https://lore.kernel.org/lkml/00000000000005c65d05a2b90e70@google.com/
>
> (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.
Powered by blists - more mailing lists