From: syzbot <syzbot+9c957444e37d521b3b94@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, lizhi.xu@windriver.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bluetooth?] general protection fault in bcsp_close
Date: Thu, 20 Feb 2025 17:24:02 -0800 [thread overview]
Message-ID: <67b7d5b2.050a0220.14d86d.0304.GAE@google.com> (raw)
In-Reply-To: <20250221010023.1766355-1-lizhi.xu@windriver.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
<stdin>:4:15: error: use of undeclared identifier '__ref_stack_chk_guard'
Tested on:
commit: 50a0c754 Add linux-next specific files for 20250220
git tree: linux-next
kernel config: https://syzkaller.appspot.com/x/.config?x=4e945b2fe8e5992f
dashboard link: https://syzkaller.appspot.com/bug?extid=9c957444e37d521b3b94
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=162567f8580000
next parent reply other threads:[~2025-02-21 1:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250221010023.1766355-1-lizhi.xu@windriver.com>
2025-02-21 1:24 ` syzbot [this message]
2025-02-20 16:00 [syzbot] [bluetooth?] general protection fault in bcsp_close syzbot
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=67b7d5b2.050a0220.14d86d.0304.GAE@google.com \
--to=syzbot+9c957444e37d521b3b94@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--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