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 13:58:27 -0400
Message-Id: <AFD0DADD-0558-463F-B219-5F098E6C2EDF@lca.pw>
References: <CAHk-=wjfngA7nHAsie7bW_JmKBhUyV9oV7zmDbZuchkJK3sR1w@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-=wjfngA7nHAsie7bW_JmKBhUyV9oV7zmDbZuchkJK3sR1w@mail.gmail.com>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


> On Apr 9, 2020, at 1:05 PM, Linus Torvalds <torvalds@linux-foundation.org>=
 wrote:
>=20
> Well, probably not very many people outside of robots.
>=20
> Which is fine, but is also why I'd like robot failures to then be a big de=
al.

Agree to make a big deal part. My point is that when kicking trees of linux-=
next, it also could reduce the exposure of many patches (which could be bad)=
 to linux-next and miss valuable early testing either from robots or human. T=
hus, the same mistakes could happen again because maintainers could simply p=
ush those little or none linux-next exposure patches to mainline with no res=
trictions. There is a balance to strike.