Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <0000000000004a33a005b8b8eaab@google.com> <20210112194058.GA200254@ubuntu-m3-large-x86>
 <CACT4Y+YFZf=BnCQJQUYwG-UpaYKG97VD-XWpEdXoR3ZnOxH5NQ@mail.gmail.com>
 <CACT4Y+Z-f+r_Bm5RD+ZFrspHdVrDrzPgEB_9_uACa_8o4vz7aw@mail.gmail.com> <CAKwvOdmBGNK0iVCAGc=7oKx9k1fE1C6y7G9S+hCYLmdu5kaKLQ@mail.gmail.com>
In-Reply-To: <CAKwvOdmBGNK0iVCAGc=7oKx9k1fE1C6y7G9S+hCYLmdu5kaKLQ@mail.gmail.com>
From:   Marco Elver <elver@google.com>
Date:   Thu, 14 Jan 2021 20:54:42 +0100
Message-ID: <CANpmjNMmObBWzHqcQ2VHru2Tdu8k0KOkVUE2upPitsOh3OoF3Q@mail.gmail.com>
Subject: Re: upstream build error (12)
To:     Nick Desaulniers <ndesaulniers@google.com>
Cc:     Dmitry Vyukov <dvyukov@google.com>,
        Nathan Chancellor <natechancellor@gmail.com>,
        syzbot <syzbot+76880518931d755473cf@syzkaller.appspotmail.com>,
        LKML <linux-kernel@vger.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@googlegroups.com>,
        clang-built-linux <clang-built-linux@googlegroups.com>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, 14 Jan 2021 at 19:07, Nick Desaulniers <ndesaulniers@google.com> wrote:
> On Thu, Jan 14, 2021 at 4:38 AM 'Dmitry Vyukov' via Clang Built Linux
> <clang-built-linux@googlegroups.com> wrote:
> >
> > On Thu, Jan 14, 2021 at 12:32 PM Dmitry Vyukov <dvyukov@google.com> wrote:
> > >
> > > On Tue, Jan 12, 2021 at 8:41 PM Nathan Chancellor
> > > <natechancellor@gmail.com> wrote:
> > > >
> > > > Would it be possible for clang-built-linux@googlegroups.com to be CC'd
> > > > when there is a build error and the compiler is clang? Especially if
> > > > clang is hitting an assertion.
> > >
> > > Hi Nathan,
> > >
> > > I am adding functionality to CC specific emails on build errors on
> > > specific instances:
> > > https://github.com/google/syzkaller/pull/2388
> >
> > I've updated configs to CC clang-built-linux@googlegroups.com. This
> > should take effect on the next build failure (hopefully).
>
> Thanks Dmitry, (and thanks Marco for updating syzbot's clang).
>
> Marco, can you update:
> https://github.com/google/syzkaller/blob/master/docs/syzbot.md#crash-does-not-reproduce

We have:

> compiler:       clang version 11.0.0 (https://github.com/llvm/llvm-project.git ca2dcbd030eadbf0aa9b660efe864ff08af6e18b)

Which is in the list of compilers:
https://storage.googleapis.com/syzkaller/clang-11-prerelease-ca2dcbd030e.tar.xz

> I wasn't able to reproduce the reported compiler crash with ToT llvm
> and the reported config, so I assume it was a mid-release of llvm-11
> bug that has since been fixed.  Do we need to report to syzbot to
> close the issue? I did a quick skim of
> https://github.com/google/syzkaller/blob/master/docs/syzbot.md, but it
> looks like communication with syzbot is based on commit messages?

Given we this is likely due to a prerelease compiler, we can just use:

#syz invalid

^^ it should pick this up.

Thanks,
-- Marco