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 21:35:02 -0700 [thread overview]
Message-ID: <68db5df6.a00a0220.102ee.0042.GAE@google.com> (raw)
In-Reply-To: <tencent_9DCD93762363A97943B5A44E7760377DE605@qq.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+ba71155d3eacc8f42477@syzkaller.appspotmail.com
Tested-by: syzbot+ba71155d3eacc8f42477@syzkaller.appspotmail.com
Tested on:
commit: 083fc6d7 Merge tag 'sched-urgent-2025-09-26' of git://..
git tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
console output: https://syzkaller.appspot.com/x/log.txt?x=12d02334580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5b21423ca3f0a96
dashboard link: https://syzkaller.appspot.com/bug?extid=ba71155d3eacc8f42477
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=137706e2580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-09-30 4:35 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
2025-09-30 4:04 ` Edward Adam Davis
2025-09-30 4:35 ` syzbot [this message]
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=68db5df6.a00a0220.102ee.0042.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