From: Marco Elver <elver@google.com>
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>
Subject: Re: upstream build error (12)
Date: Thu, 14 Jan 2021 20:54:42 +0100 [thread overview]
Message-ID: <CANpmjNMmObBWzHqcQ2VHru2Tdu8k0KOkVUE2upPitsOh3OoF3Q@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOdmBGNK0iVCAGc=7oKx9k1fE1C6y7G9S+hCYLmdu5kaKLQ@mail.gmail.com>
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
prev parent reply other threads:[~2021-01-14 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 19:20 upstream build error (12) syzbot
2021-01-12 19:40 ` Nathan Chancellor
2021-01-12 20:32 ` Nathan Chancellor
2021-01-12 20:44 ` Marco Elver
2021-01-14 11:32 ` Dmitry Vyukov
2021-01-14 12:37 ` Dmitry Vyukov
2021-01-14 18:06 ` Nick Desaulniers
2021-01-14 19:54 ` Marco Elver [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANpmjNMmObBWzHqcQ2VHru2Tdu8k0KOkVUE2upPitsOh3OoF3Q@mail.gmail.com \
--to=elver@google.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dvyukov@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=syzbot+76880518931d755473cf@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).