From: syzbot <syzbot+a5e651ca75fa0260acd5@syzkaller.appspotmail.com>
To: chao@kernel.org, eadavis@qq.com, ebiggers@google.com,
jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] KASAN: slab-use-after-free Read in destroy_device_list
Date: Sat, 13 Jan 2024 20:59:04 -0800 [thread overview]
Message-ID: <0000000000009fff64060ee0c1b7@google.com> (raw)
In-Reply-To: <000000000000aac725060ed0b15c@google.com>
syzbot has bisected this issue to:
commit 275dca4630c165edea9abe27113766bc1173f878
Author: Eric Biggers <ebiggers@google.com>
Date: Wed Dec 27 17:14:28 2023 +0000
f2fs: move release of block devices to after kill_block_super()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=10639913e80000
start commit: 052d534373b7 Merge tag 'exfat-for-6.8-rc1' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=12639913e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=14639913e80000
kernel config: https://syzkaller.appspot.com/x/.config?x=878a2a4af11180a7
dashboard link: https://syzkaller.appspot.com/bug?extid=a5e651ca75fa0260acd5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=167b0f47e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11255313e80000
Reported-by: syzbot+a5e651ca75fa0260acd5@syzkaller.appspotmail.com
Fixes: 275dca4630c1 ("f2fs: move release of block devices to after kill_block_super()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-01-14 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-13 9:49 [syzbot] [f2fs?] KASAN: slab-use-after-free Read in destroy_device_list syzbot
2024-01-13 11:28 ` [PATCH] f2fs: fix uaf " Edward Adam Davis
2024-01-14 4:59 ` syzbot [this message]
2024-01-18 3:58 ` [syzbot] [f2fs?] KASAN: slab-use-after-free Read " Eric Biggers
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=0000000000009fff64060ee0c1b7@google.com \
--to=syzbot+a5e651ca75fa0260acd5@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=eadavis@qq.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).