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  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]
Date:   Tue, 12 Jan 2021 12:40:58 -0700
From:   Nathan Chancellor <>
To:     syzbot <>
Subject: Re: upstream build error (12)

On Tue, Jan 12, 2021 at 11:20:27AM -0800, syzbot wrote:
> Hello,
> syzbot found the following issue on:
> HEAD commit:    e609571b Merge tag 'nfs-for-5.11-2' of git://git.linux-nfs..
> git tree:       upstream
> console output:
> kernel config:
> dashboard link:
> compiler:       clang version 11.0.0 ( ca2dcbd030eadbf0aa9b660efe864ff08af6e18b)
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by:
> clang-11: error: unable to execute command: Aborted (core dumped)
> clang-11: error: clang frontend command failed due to signal (use -v to see invocation)
> ---
> This report is generated by a bot. It may contain errors.
> See for more information about syzbot.
> syzbot engineers can be reached at
> syzbot will keep track of this issue. See:
> for how to communicate with syzbot.

Would it be possible for to be CC'd
when there is a build error and the compiler is clang? Especially if
clang is hitting an assertion.


Powered by blists - more mailing lists