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 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?

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_.

           Linus




[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