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;
Date:   Fri, 10 Apr 2020 09:29:51 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Linus Torvalds <torvalds@linux-foundation.org>
Cc:     Dmitry Vyukov <dvyukov@google.com>,
        Andrew Morton <akpm@linux-foundation.org>,
        Peter Xu <peterx@redhat.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH 0/2] mm: Two small fixes for recent syzbot reports
Message-ID: <20200410092951.6db32bfe@canb.auug.org.au>
In-Reply-To: <CAHk-=wgjGgfUfVm_DpTay5TS03pLCgUWqRpQS++90fSE2V-e=g@mail.gmail.com>
References: <20200408014010.80428-1-peterx@redhat.com>
        <20200408174732.bc448bbe41d190bfe5cc252e@linux-foundation.org>
        <CACT4Y+bhQVcpSkSh_OZ5ZanfFZUqn2iypLhG_Z-nWKTkaYr1jw@mail.gmail.com>
        <CAHk-=wgjGgfUfVm_DpTay5TS03pLCgUWqRpQS++90fSE2V-e=g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/n_a=u.Ml/2pJE9BUl5munRl";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

--Sig_/n_a=u.Ml/2pJE9BUl5munRl
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi Linus,

On Thu, 9 Apr 2020 09:32:32 -0700 Linus Torvalds <torvalds@linux-foundation=
.org> wrote:
>
> On Thu, Apr 9, 2020 at 5:55 AM Dmitry Vyukov <dvyukov@google.com> wrote:
> >
> > linux-next is boot-broken for more than a month and bugs are piling
> > onto bugs, I've seen at least 3 different ones.
> > syzbot can't get any working linux-next build for testing for a very
> > long time now. =20
>=20
> Ouch.
>=20
> Ok, that's not good. It means that linux-next has basically only done
> build-testing this whole cycle.

Well, there are other CI's beyond syzbot .. Does syzbot only build/test
a single kernel arch/config?

> Stephen, Dmitry - is there some way linux-next could possibly kick out
> trees more aggressively if syzbot can't even boot?

Of course that could be done if I knew that there were problems.  From
memory and my mail archives, I was only cc'd on 3 problems by sysbot
since last November and they were all responded to by the appropriate
maintainers/developers.

Currently, when I am cc'd on reports, if they are also sent to who
seem like the appropriate people, I just file the report assuming it
will be dealt with.

> Kicking trees out of linux-next and making noise if they cause syzbot
> failures might also make some maintainers react more..

That may be true, but in some cases I have carried fixups/reverts/older
versions of trees for quite some time before things get fixed.  But at
least if that happens, I do tend to remind people.

--=20
Cheers,
Stephen Rothwell

--Sig_/n_a=u.Ml/2pJE9BUl5munRl
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl6Pr+8ACgkQAVBC80lX
0GwCHgf/ZRqpSjhVVe+fYBrYmpnwfFnrL/Oh72lh7tck0j1YEjzwMCFBfN5pijAv
WMI80UlZlDlj3L6ErGNnlkkHuQr+qDmXXPfPFGHXkVYKxf7Wm4653D+xjz5ON1qH
ynkN7384PaKE/o23MokpEvxP8/l7pPMhT0nQeJtY76c/tPDaBVg5vN9cOH+4poZm
KvExSzx242t12kd0m0tqCQSnnNVJKdOdZ5XJ/oCc8oaq8n8t095FfXM+TNffwHkg
N+U17MlvBmmsOetOZ+MhV8BzKyixzKyYgDiNnn8FBgyhCcEae1LEeUaW0qM/um4V
nPrJdvinKjPgPth7YtGGTcHG2iBMsw==
=2xaa
-----END PGP SIGNATURE-----

--Sig_/n_a=u.Ml/2pJE9BUl5munRl--