linux-kernel - Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wgy3XRiyRP7vdfF6bHwWGaB1RwyWJmyphh+Q3qYk6w27w@mail.gmail.com>
Date:   Thu, 9 Apr 2020 12:46:08 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Andrew Morton <akpm@...ux-foundation.org>
Cc:     Dmitry Vyukov <dvyukov@...gle.com>,
        Matthew Wilcox <willy@...radead.org>,
        Peter Xu <peterx@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux-MM <linux-mm@...ck.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        syzkaller <syzkaller@...glegroups.com>
Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports

On Thu, Apr 9, 2020 at 12:12 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> And now the challenge is to protect your tree from the bad patches.

Well, right now, yes.

But in the longer term, I think we want to protect linux-next from the
bad patches so that they don't poison the testing that the bots can
do.

So that's why I suggested that linux-next and syzbot have some
protocol to have things that cause syzbot pain to be removed from
linux-next more aggressively.

              Linus