From: syzbot <syzbot+ba71155d3eacc8f42477@syzkaller.appspotmail.com>
To: eadavis@qq.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_btree_node_read_done
Date: Mon, 29 Sep 2025 20:44:02 -0700 [thread overview]
Message-ID: <68db5202.a70a0220.10c4b.00e6.GAE@google.com> (raw)
In-Reply-To: <tencent_E5865E49816ED4AEC2CC9AA7DF86CC12E706@qq.com>
Hello,
syzbot tried to test the proposed patch but the build/boot failed:
failed to apply patch:
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/fs/bcachefs/btree_io.c b/fs/bcachefs/btree_io.c
|index 590cd29f3e86..ab14fff1452f 100644
|--- a/fs/bcachefs/btree_io.c
|+++ b/fs/bcachefs/btree_io.c
--------------------------
No file to patch. Skipping patch.
1 out of 1 hunk ignored
Tested on:
commit: 30d4efb2 Merge tag 'for-linus-6.18-rc1-tag' of git://g..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=f5b21423ca3f0a96
dashboard link: https://syzkaller.appspot.com/bug?extid=ba71155d3eacc8f42477
compiler:
patch: https://syzkaller.appspot.com/x/patch.diff?x=16afc334580000
next prev parent reply other threads:[~2025-09-30 3:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 18:49 [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_btree_node_read_done syzbot
2025-09-30 3:42 ` Edward Adam Davis
2025-09-30 3:44 ` syzbot [this message]
2025-09-30 4:04 ` Edward Adam Davis
2025-09-30 4:35 ` syzbot
2025-09-30 5:11 ` [PATCH] bcachefs: Prevent written from exceeding sectors Edward Adam Davis
2025-09-30 20:46 ` kernel test robot
2025-10-01 0:19 ` [PATCH V2] " Edward Adam Davis
2025-11-07 0:50 ` [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_btree_node_read_done 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=68db5202.a70a0220.10c4b.00e6.GAE@google.com \
--to=syzbot+ba71155d3eacc8f42477@syzkaller.appspotmail.com \
--cc=eadavis@qq.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox