From: syzbot <syzbot+b8639c8dcb5ec4483d4f@syzkaller.appspotmail.com>
To: anant.thazhemadam@gmail.com, axboe@kernel.dk,
bgolaszewski@baylibre.com, dan.j.williams@intel.com,
dragonjetli@gmail.com, gregkh@linuxfoundation.org, hch@lst.de,
hl1998@protonmail.com, jack@suse.cz, jean-philippe@linaro.org,
johannes.thumshirn@wdc.com, jroedel@suse.de,
linux-block@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org, rafael@kernel.org,
saravanak@google.com, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in delete_partition
Date: Wed, 07 Oct 2020 20:38:09 -0700 [thread overview]
Message-ID: <0000000000008dab1205b1208fe6@google.com> (raw)
In-Reply-To: <0000000000009323e705ae870d48@google.com>
syzbot suspects this issue was fixed by commit:
commit 08fc1ab6d748ab1a690fd483f41e2938984ce353
Author: Christoph Hellwig <hch@lst.de>
Date: Tue Sep 1 09:59:41 2020 +0000
block: fix locking in bdev_del_partition
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1259b1e7900000
start commit: f75aef39 Linux 5.9-rc3
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299
dashboard link: https://syzkaller.appspot.com/bug?extid=b8639c8dcb5ec4483d4f
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15c43c79900000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=173dfa1e900000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: block: fix locking in bdev_del_partition
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2020-10-08 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-05 1:39 KASAN: use-after-free Read in delete_partition syzbot
2020-10-08 3:38 ` syzbot [this message]
2020-11-11 11:13 ` Dmitry Vyukov
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=0000000000008dab1205b1208fe6@google.com \
--to=syzbot+b8639c8dcb5ec4483d4f@syzkaller.appspotmail.com \
--cc=anant.thazhemadam@gmail.com \
--cc=axboe@kernel.dk \
--cc=bgolaszewski@baylibre.com \
--cc=dan.j.williams@intel.com \
--cc=dragonjetli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=hl1998@protonmail.com \
--cc=jack@suse.cz \
--cc=jean-philippe@linaro.org \
--cc=johannes.thumshirn@wdc.com \
--cc=jroedel@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@google.com \
--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).