From: syzbot <syzbot+06fd1a3613c50d36129e@syzkaller•appspotmail.com>
To: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
sfr@canb•auug.org.au, syzkaller-bugs@googlegroups•com
Subject: [syzbot] linux-next build error (20)
Date: Sat, 22 Feb 2025 22:02:24 -0800 [thread overview]
Message-ID: <67bab9f0.050a0220.bbfd1.000e.GAE@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: d4b0fd87ff0d Add linux-next specific files for 20250221
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17a5bae4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=76d7299d72819017
dashboard link: https://syzkaller.appspot.com/bug?extid=06fd1a3613c50d36129e
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+06fd1a3613c50d36129e@syzkaller•appspotmail.com
<stdin>:4:15: error: use of undeclared identifier '__ref_stack_chk_guard'
---
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
next reply other threads:[~2025-02-23 6:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-23 6:02 syzbot [this message]
2025-03-19 5:10 ` [syzbot] linux-next build error (20) Aleksandr Nogikh
2025-03-19 8:38 ` Ard Biesheuvel
2025-03-19 18:45 ` Sami Tolvanen
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=67bab9f0.050a0220.bbfd1.000e.GAE@google.com \
--to=syzbot+06fd1a3613c50d36129e@syzkaller$(echo .)appspotmail.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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