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: <BB768A53-4A6F-4C69-8FBC-8BCAB1F4F280@lca.pw>
Date:   Thu, 9 Apr 2020 12:58:45 -0400
From:   Qian Cai <cai@....pw>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Dmitry Vyukov <dvyukov@...gle.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Peter Xu <peterx@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Linux-MM <linux-mm@...ck.org>
Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports

> On Apr 9, 2020, at 12:32 PM, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> 
> Kicking trees out of linux-next and making noise if they cause syzbot
> failures might also make some maintainers react more..

On the other hand, this makes me worry who is testing on linux-next every day. The worst nightmare I am having right now is some maintainers pick up commits that only have been in -next for a few days and then push to the mainline but then it is becoming my burden to fix those commits in case they introduced regressions because it is much harder to revert patches once in mainline.

Kicking out of trees in linux-next on the other hand could make the situation worst unless we have a counter solution that make sure commits must be in -next for a certain time (a month?) before merged in mainline.