From: syzbot <syzbot+5138f00559ffb3cb3610@syzkaller.appspotmail.com>
To: abhinav.ogl@gmail.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v2_to_text
Date: Thu, 05 Jun 2025 13:49:04 -0700 [thread overview]
Message-ID: <684202c0.a70a0220.21738b.002a.GAE@google.com> (raw)
In-Reply-To: <CAGR7w81B2saOi5NPpK4FKtwbq6c1nQL1JazQrcKBK7W4jJpD-w@mail.gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+5138f00559ffb3cb3610@syzkaller.appspotmail.com
Tested-by: syzbot+5138f00559ffb3cb3610@syzkaller.appspotmail.com
Tested on:
commit: 4f27f06e Add linux-next specific files for 20250605
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17348c0c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=28859360c84ac63d
dashboard link: https://syzkaller.appspot.com/bug?extid=5138f00559ffb3cb3610
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6
patch: https://syzkaller.appspot.com/x/patch.diff?x=17dd0c0c580000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-06-05 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGR7w81B2saOi5NPpK4FKtwbq6c1nQL1JazQrcKBK7W4jJpD-w@mail.gmail.com>
2025-06-05 20:49 ` syzbot [this message]
[not found] <CAGR7w80YXbHHLoSt+CMGAroarTFe2jMXqvJRddpgmbV9=GLK1Q@mail.gmail.com>
2025-06-09 16:18 ` [syzbot] [bcachefs?] KASAN: slab-out-of-bounds Read in bch2_sb_members_v2_to_text syzbot
[not found] <CAGR7w82GyV+37kyf+y6NzSxrkeHqhjzaerC6mEqBJ1b4ACzz9g@mail.gmail.com>
2025-06-05 16:14 ` syzbot
[not found] <CAGR7w82+NvTjNtc-Bvf0A02BFqZPPrXTr3e9iqaBTLoLyRwF6g@mail.gmail.com>
2025-06-04 14:04 ` syzbot
2025-05-26 10: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=684202c0.a70a0220.21738b.002a.GAE@google.com \
--to=syzbot+5138f00559ffb3cb3610@syzkaller.appspotmail.com \
--cc=abhinav.ogl@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.