From: syzbot <syzbot+fbc1f6040dd365cce0d8@syzkaller.appspotmail.com>
To: davthompson@nvidia.com, ilpo.jarvinen@linux.intel.com,
kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
xiangrongl@nvidia.com
Subject: Re: [syzbot] [bcachefs?] KASAN: use-after-free Read in check_extent_overbig
Date: Sat, 26 Apr 2025 23:48:01 -0700 [thread overview]
Message-ID: <680dd321.050a0220.2b69d1.001a.GAE@google.com> (raw)
In-Reply-To: <6751e9fb.050a0220.b4160.01e2.GAE@google.com>
syzbot suspects this issue was fixed by commit:
commit 5d40a8577559250029ff571de38ffcbc226a63d7
Author: Xiangrong Li <xiangrongl@nvidia.com>
Date: Fri Jan 24 14:46:55 2025 +0000
mlxbf-bootctl: Support sysfs entries for RTC battery status
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=126f9d74580000
start commit: feffde684ac2 Merge tag 'for-6.13-rc1-tag' of git://git.ker..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=91c852e3d1d7c1a6
dashboard link: https://syzkaller.appspot.com/bug?extid=fbc1f6040dd365cce0d8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=16804020580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12ed1330580000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: mlxbf-bootctl: Support sysfs entries for RTC battery status
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-04-27 6:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 17:59 [syzbot] [bcachefs?] KASAN: use-after-free Read in check_extent_overbig syzbot
2024-12-06 6:11 ` syzbot
2025-04-27 6:48 ` syzbot [this message]
2025-07-19 19:17 ` Kent Overstreet
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=680dd321.050a0220.2b69d1.001a.GAE@google.com \
--to=syzbot+fbc1f6040dd365cce0d8@syzkaller.appspotmail.com \
--cc=davthompson@nvidia.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiangrongl@nvidia.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