From: syzbot <syzbot+1f0620b0141e43a84282@syzkaller.appspotmail.com>
To: ast@kernel.org, daniel@iogearbox.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] bpf-next build error (6)
Date: Mon, 01 Apr 2024 23:36:25 -0700 [thread overview]
Message-ID: <000000000000468fff06151753a0@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: e478cf26c556 Merge branch 'bpf-fix-a-couple-of-test-failur..
git tree: bpf-next
console output: https://syzkaller.appspot.com/x/log.txt?x=168bc92d180000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b667bc37450fdcd
dashboard link: https://syzkaller.appspot.com/bug?extid=1f0620b0141e43a84282
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+1f0620b0141e43a84282@syzkaller.appspotmail.com
failed to run ["make" "-j" "64" "ARCH=x86_64" "CC=clang" "bzImage"]: exit status 2
---
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.
If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title
If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)
If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report
If you want to undo deduplication, reply with:
#syz undup
reply other threads:[~2024-04-02 6:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000468fff06151753a0@google.com \
--to=syzbot+1f0620b0141e43a84282@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox