From: syzbot <syzbot+d1b7fa1092def3628bd7@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, listout@listout.xyz,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bpf?] KASAN: stack-out-of-bounds Write in __bpf_get_stack
Date: Mon, 10 Nov 2025 16:22:03 -0800 [thread overview]
Message-ID: <691281ab.a70a0220.22f260.0115.GAE@google.com> (raw)
In-Reply-To: <xgynmmyztqi2kkzhchyzgzd2clszohjy4vinzb2ij4qyvdz4mc@36tdk5l7bq5s>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
checking file kernel/bpf/stackmap.c
Hunk #1 FAILED at 480.
1 out of 1 hunk FAILED
Tested on:
commit: f8c67d85 bpf: Use kmalloc_nolock() in range tree
git tree: bpf-next
kernel config: https://syzkaller.appspot.com/x/.config?x=e46b8a1c645465a9
dashboard link: https://syzkaller.appspot.com/bug?extid=d1b7fa1092def3628bd7
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=114e7084580000
next parent reply other threads:[~2025-11-11 0:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xgynmmyztqi2kkzhchyzgzd2clszohjy4vinzb2ij4qyvdz4mc@36tdk5l7bq5s>
2025-11-11 0:22 ` syzbot [this message]
2026-01-04 18:30 #syz test Arnaud Lecomte
2026-01-04 20:43 ` [syzbot] [bpf?] KASAN: stack-out-of-bounds Write in __bpf_get_stack syzbot
-- strict thread matches above, loose matches on Subject: below --
2026-01-04 18:29 #syz test Arnaud Lecomte
2026-01-04 20:09 ` [syzbot] [bpf?] KASAN: stack-out-of-bounds Write in __bpf_get_stack syzbot
[not found] <nytg5vjyof6he3v46kqhhyqochwgpk7bjx2topppykhqmw6kds@pin7crrdgg2i>
2025-11-11 2:28 ` syzbot
[not found] <iattottzq4koautrgwq74vaxrohcqpfcxarygoyroaimoorggg@g6lxrp34lajg>
2025-11-10 21:34 ` syzbot
[not found] <6fyxpa6cocnr4hbpmzrwel4t2huouz5p4ul6qawttjzlgmuysn@hcleklvgi464>
2025-11-10 19:50 ` syzbot
[not found] <ckkn76mbmurstoxlhjfnrwjht2hydo3daius5kc42j6s3nsc2o@d4ftoisfyii5>
2025-11-10 19:33 ` syzbot
2025-11-10 18:41 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=691281ab.a70a0220.22f260.0115.GAE@google.com \
--to=syzbot+d1b7fa1092def3628bd7@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=listout@listout.xyz \
--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