All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+8f477ac014ff5b32d81f@syzkaller.appspotmail.com>
To: chao@kernel.org, ebiggers@google.com, ebiggers@kernel.org,
	 hdanton@sina.com, jaegeuk@kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	 linux-fscrypt@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	 linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] KASAN: slab-use-after-free Read in kill_f2fs_super
Date: Fri, 12 Jan 2024 22:38:04 -0800	[thread overview]
Message-ID: <000000000000d65af9060ece0537@google.com> (raw)
In-Reply-To: <0000000000006cb174060ec34502@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=16071613e80000
start commit:   70d201a40823 Merge tag 'f2fs-for-6.8-rc1' of git://git.ker..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=15071613e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=11071613e80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4607bc15d1c4bb90
dashboard link: https://syzkaller.appspot.com/bug?extid=8f477ac014ff5b32d81f
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=112b660be80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14c1df5de80000

Reported-by: syzbot+8f477ac014ff5b32d81f@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


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+8f477ac014ff5b32d81f@syzkaller.appspotmail.com>
To: chao@kernel.org, ebiggers@google.com, ebiggers@kernel.org,
	 hdanton@sina.com, jaegeuk@kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	 linux-fscrypt@vger.kernel.org, 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 kill_f2fs_super
Date: Fri, 12 Jan 2024 22:38:04 -0800	[thread overview]
Message-ID: <000000000000d65af9060ece0537@google.com> (raw)
In-Reply-To: <0000000000006cb174060ec34502@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=16071613e80000
start commit:   70d201a40823 Merge tag 'f2fs-for-6.8-rc1' of git://git.ker..
git tree:       upstream
final oops:     https://syzkaller.appspot.com/x/report.txt?x=15071613e80000
console output: https://syzkaller.appspot.com/x/log.txt?x=11071613e80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4607bc15d1c4bb90
dashboard link: https://syzkaller.appspot.com/bug?extid=8f477ac014ff5b32d81f
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=112b660be80000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=14c1df5de80000

Reported-by: syzbot+8f477ac014ff5b32d81f@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

  parent reply	other threads:[~2024-01-13  6:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 17:48 [f2fs-dev] [syzbot] [f2fs?] KASAN: slab-use-after-free Read in kill_f2fs_super syzbot
2024-01-12 17:48 ` syzbot
2024-01-12 18:14 ` [f2fs-dev] " syzbot
2024-01-12 18:14   ` syzbot
2024-01-13  1:50   ` Hillf Danton
2024-01-13  2:14     ` syzbot
2024-01-13  0:32 ` [f2fs-dev] " syzbot
2024-01-13  0:32   ` syzbot
2024-01-13  0:50   ` [f2fs-dev] " Eric Biggers
2024-01-13  0:50     ` Eric Biggers
2024-01-13  0:57     ` [f2fs-dev] [PATCH] f2fs: fix double free of f2fs_sb_info Eric Biggers
2024-01-13  0:57       ` Eric Biggers
2024-01-13  1:01       ` [f2fs-dev] " Eric Biggers
2024-01-13  1:01         ` Eric Biggers
2024-01-13  1:28         ` [f2fs-dev] " Jaegeuk Kim
2024-01-13  1:28           ` Jaegeuk Kim
2024-01-13  1:32           ` [f2fs-dev] " Eric Biggers
2024-01-13  1:32             ` Eric Biggers
2024-01-13  1:46             ` [f2fs-dev] " Jaegeuk Kim
2024-01-13  1:46               ` Jaegeuk Kim
2024-01-13  1:14       ` [f2fs-dev] " Chao Yu
2024-01-13  1:14         ` Chao Yu
2024-01-13  6:38 ` syzbot [this message]
2024-01-13  6:38   ` [syzbot] [f2fs?] KASAN: slab-use-after-free Read in kill_f2fs_super syzbot
2024-01-18  3:59   ` [f2fs-dev] " Eric Biggers
2024-01-18  3:59     ` 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=000000000000d65af9060ece0537@google.com \
    --to=syzbot+8f477ac014ff5b32d81f@syzkaller.appspotmail.com \
    --cc=chao@kernel.org \
    --cc=ebiggers@google.com \
    --cc=ebiggers@kernel.org \
    --cc=hdanton@sina.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fscrypt@vger.kernel.org \
    --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 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.