From: syzbot <syzbot+fbc1f6040dd365cce0d8@syzkaller.appspotmail.com>
To: kent.overstreet@linux.dev, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [bcachefs?] KASAN: use-after-free Read in check_extent_overbig
Date: Thu, 05 Dec 2024 22:11:02 -0800 [thread overview]
Message-ID: <67529576.050a0220.a30f1.0131.GAE@google.com> (raw)
In-Reply-To: <6751e9fb.050a0220.b4160.01e2.GAE@google.com>
syzbot has bisected this issue to:
commit bf4baaa087e2be0279991f1dbf9acaa7a4c9148c
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Sat Oct 5 21:37:02 2024 +0000
bcachefs: Fix lockdep splat in bch2_accounting_read
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1147e8df980000
start commit: feffde684ac2 Merge tag 'for-6.13-rc1-tag' of git://git.ker..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=1347e8df980000
console output: https://syzkaller.appspot.com/x/log.txt?x=1547e8df980000
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
Reported-by: syzbot+fbc1f6040dd365cce0d8@syzkaller.appspotmail.com
Fixes: bf4baaa087e2 ("bcachefs: Fix lockdep splat in bch2_accounting_read")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-12-06 6:11 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 [this message]
2025-04-27 6:48 ` syzbot
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=67529576.050a0220.a30f1.0131.GAE@google.com \
--to=syzbot+fbc1f6040dd365cce0d8@syzkaller.appspotmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--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.