From: syzbot <syzbot+6663075ddb9be85fa6e5@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, david@fromorbit.com,
gfs2@lists.linux.dev, hughd@google.com,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mmpgouride@gmail.com, muchun.song@linux.dev,
roman.gushchin@linux.dev, syzkaller-bugs@googlegroups.com,
zhengqi.arch@bytedance.com
Subject: Re: [syzbot] [mm?] KASAN: slab-use-after-free Read in list_lru_del
Date: Tue, 30 Dec 2025 17:42:02 -0800 [thread overview]
Message-ID: <69547f6a.050a0220.a1b6.0308.GAE@google.com> (raw)
In-Reply-To: <67a4eae3.050a0220.65602.0001.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 3a04334d6282d08fbdd6201e374db17d31927ba3
Author: Alan Huang <mmpgouride@gmail.com>
Date: Fri Mar 7 16:58:27 2025 +0000
bcachefs: Fix b->written overflow
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=117f329a580000
start commit: 03d38806a902 Merge tag 'thermal-6.14-rc5' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=8de9cc84d5960254
dashboard link: https://syzkaller.appspot.com/bug?extid=6663075ddb9be85fa6e5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=104d2864580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: bcachefs: Fix b->written overflow
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-12-31 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 17:01 [syzbot] [mm?] [bcachefs?] " syzbot
2025-03-07 22:42 ` syzbot
2025-11-28 21:46 ` [syzbot] [mm?] " syzbot
2025-11-29 18:34 ` Andrew Morton
2025-12-31 1:42 ` syzbot [this message]
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=69547f6a.050a0220.a1b6.0308.GAE@google.com \
--to=syzbot+6663075ddb9be85fa6e5@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=gfs2@lists.linux.dev \
--cc=hughd@google.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mmpgouride@gmail.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=zhengqi.arch@bytedance.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