On Thu, 9 Apr 2020 11:53:33 -0700 Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
> On Thu, Apr 9, 2020 at 11:16 AM Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> >
> > Could I please direct attention back to my original question regarding
> > the problems we've recently discovered in 4426e945df58 ("mm/gup: allow
> > VM_FAULT_RETRY for multiple times") and 71335f37c5e8 ("mm/gup: allow to
> > react to fatal signals")?
>
> What earlier question? The "how could this happen" one?
>
> Dmitry already answered that one - are you perhaps missing the emails?
Yup, email threading got broken.
> linux-next has apparently not worked at all for over a month. So it
> got no testing at all, and thus also all the gup patches got no
> testing in linux-next.
>
> Only when they hit my tree, did they start getting testing. Not
> because my tree is the only thing getting tested, but because my tree
> is the only tree that _works_.
>
And now the challenge is to protect your tree from the bad patches.
https://groups.google.com/forum/#!msg/syzkaller-bugs/phowYdNXHck/qU1P0TsjBAAJ
points at
net/openvswitch/conntrack.c
net/bluetooth/l2cap_sock.c
sound/core/oss/pcm_plugin.c
and other things, but it's 2+ weeks old.
