From: syzbot <syzbot+6448f3c229bc52b82f69@syzkaller.appspotmail.com>
To: axboe@kernel.dk, hch@lst.de, jack@suse.cz,
johannes.thumshirn@wdc.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in bdev_del_partition
Date: Mon, 31 Aug 2020 13:29:07 -0700 [thread overview]
Message-ID: <0000000000001985dc05ae32417b@google.com> (raw)
In-Reply-To: <000000000000520ffc05ae2f4fee@google.com>
syzbot has bisected this issue to:
commit cddae808aeb77e5c29d22a8e0dfbdaed413f9e04
Author: Christoph Hellwig <hch@lst.de>
Date: Tue Apr 14 07:28:54 2020 +0000
block: pass a hd_struct to delete_partition
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17fa7656900000
start commit: dcc5c6f0 Merge tag 'x86-urgent-2020-08-30' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14067656900000
console output: https://syzkaller.appspot.com/x/log.txt?x=10067656900000
kernel config: https://syzkaller.appspot.com/x/.config?x=891ca5711a9f1650
dashboard link: https://syzkaller.appspot.com/bug?extid=6448f3c229bc52b82f69
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=154e2285900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16f6e915900000
Reported-by: syzbot+6448f3c229bc52b82f69@syzkaller.appspotmail.com
Fixes: cddae808aeb7 ("block: pass a hd_struct to delete_partition")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-08-31 20:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 16:58 KASAN: use-after-free Read in bdev_del_partition syzbot
2020-08-31 20:29 ` syzbot [this message]
2020-09-02 9:31 ` Peilin Ye
2020-09-03 6:55 ` [Linux-kernel-mentees] [PATCH] block: Fix use-after-free in bdev_del_partition() Peilin Ye
2020-09-03 6:55 ` Peilin Ye
2020-09-03 6:59 ` Christoph Hellwig
2020-09-03 6:59 ` Christoph Hellwig
2020-09-03 7:23 ` Peilin Ye
2020-09-03 7:23 ` Peilin Ye
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=0000000000001985dc05ae32417b@google.com \
--to=syzbot+6448f3c229bc52b82f69@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@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.