linux-kernel - Re: upstream build error (12)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKwvOdmBGNK0iVCAGc=7oKx9k1fE1C6y7G9S+hCYLmdu5kaKLQ@mail.gmail.com>
Date:   Thu, 14 Jan 2021 10:06:54 -0800
From:   Nick Desaulniers <ndesaulniers@...gle.com>
To:     Dmitry Vyukov <dvyukov@...gle.com>, Marco Elver <elver@...gle.com>
Cc:     Nathan Chancellor <natechancellor@...il.com>,
        syzbot <syzbot+76880518931d755473cf@...kaller.appspotmail.com>,
        LKML <linux-kernel@...r.kernel.org>,
        syzkaller-bugs <syzkaller-bugs@...glegroups.com>,
        clang-built-linux <clang-built-linux@...glegroups.com>
Subject: Re: upstream build error (12)

On Thu, Jan 14, 2021 at 4:38 AM 'Dmitry Vyukov' via Clang Built Linux
<clang-built-linux@...glegroups.com> wrote:
>
> On Thu, Jan 14, 2021 at 12:32 PM Dmitry Vyukov <dvyukov@...gle.com> wrote:
> >
> > On Tue, Jan 12, 2021 at 8:41 PM Nathan Chancellor
> > <natechancellor@...il.com> wrote:
> > >
> > > Would it be possible for clang-built-linux@...glegroups.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@...glegroups.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

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?
--
Thanks,
~Nick Desaulniers