Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
From:   Qian Cai <cai@lca.pw>
Mime-Version: 1.0 (1.0)
Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports
Date:   Thu, 9 Apr 2020 12:58:45 -0400
Message-Id: <BB768A53-4A6F-4C69-8FBC-8BCAB1F4F280@lca.pw>
References: <CAHk-=wgjGgfUfVm_DpTay5TS03pLCgUWqRpQS++90fSE2V-e=g@mail.gmail.com>
Cc:     Dmitry Vyukov <dvyukov@google.com>,
        Stephen Rothwell <sfr@canb.auug.org.au>,
        Andrew Morton <akpm@linux-foundation.org>,
        Peter Xu <peterx@redhat.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Linux-MM <linux-mm@kvack.org>
In-Reply-To: <CAHk-=wgjGgfUfVm_DpTay5TS03pLCgUWqRpQS++90fSE2V-e=g@mail.gmail.com>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Apr 9, 2020, at 12:32 PM, Linus Torvalds <torvalds@linux-foundation.org=
> wrote:
>=20
> 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 da=
y. The worst nightmare I am having right now is some maintainers pick up com=
mits that only have been in -next for a few days and then push to the mainli=
ne but then it is becoming my burden to fix those commits in case they intro=
duced regressions because it is much harder to revert patches once in mainli=
ne.

Kicking out of trees in linux-next on the other hand could make the situatio=
n 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.=