From: syzbot <syzbot+87078ad27cd8af3263cc@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_dirent
Date: Fri, 21 Feb 2025 17:01:03 -0800 [thread overview]
Message-ID: <67b921cf.050a0220.14d86d.059a.GAE@google.com> (raw)
In-Reply-To: <67b8a9a7.050a0220.14d86d.0578.GAE@google.com>
syzbot has bisected this issue to:
commit cf3da2d627037a0848e25dbaeaedfadfe534c7c4
Author: Kent Overstreet <kent.overstreet@linux.dev>
Date: Mon Dec 16 18:58:02 2024 +0000
bcachefs: Handle -BCH_ERR_need_mark_replicas in gc
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10e887a4580000
start commit: 27eddbf34490 Merge tag 'net-6.14-rc4' of git://git.kernel...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12e887a4580000
console output: https://syzkaller.appspot.com/x/log.txt?x=14e887a4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b03346163189483c
dashboard link: https://syzkaller.appspot.com/bug?extid=87078ad27cd8af3263cc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ce6ba4580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11300db0580000
Reported-by: syzbot+87078ad27cd8af3263cc@syzkaller.appspotmail.com
Fixes: cf3da2d62703 ("bcachefs: Handle -BCH_ERR_need_mark_replicas in gc")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-02-22 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 16:28 [syzbot] [bcachefs?] KASAN: use-after-free Read in check_dirent syzbot
2025-02-22 1:01 ` syzbot [this message]
2025-07-19 19:19 ` 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=67b921cf.050a0220.14d86d.059a.GAE@google.com \
--to=syzbot+87078ad27cd8af3263cc@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.