All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+76880518931d755473cf@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: upstream build error (12)
Date: Tue, 12 Jan 2021 11:20:27 -0800	[thread overview]
Message-ID: <0000000000004a33a005b8b8eaab@google.com> (raw)

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: https://syzkaller.appspot.com/x/log.txt?x=15965a00d00000
kernel config:  https://syzkaller.appspot.com/x/.config?x=6157970d0a91b812
dashboard link: https://syzkaller.appspot.com/bug?extid=76880518931d755473cf
compiler:       clang version 11.0.0 (https://github.com/llvm/llvm-project.git ca2dcbd030eadbf0aa9b660efe864ff08af6e18b)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+76880518931d755473cf@syzkaller.appspotmail.com

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 https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

             reply	other threads:[~2021-01-12 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 19:20 syzbot [this message]
2021-01-12 19:40 ` upstream build error (12) 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

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=0000000000004a33a005b8b8eaab@google.com \
    --to=syzbot+76880518931d755473cf@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.