From: Ming Lei <tom.leiming@gmail.com>
To: syzbot <syzbot+8fede7e30c7cee0de139@syzkaller.appspotmail.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in disk_part_iter_next (2)
Date: Mon, 22 Mar 2021 16:51:33 +0800 [thread overview]
Message-ID: <CACVXFVO-6A_u-zNvkUt4x57gAwxJBDHx=Arc6KPKh560X3G29w@mail.gmail.com> (raw)
In-Reply-To: <00000000000053da9405bd7d2644@google.com>
On Sun, Mar 14, 2021 at 7:10 PM syzbot
<syzbot+8fede7e30c7cee0de139@syzkaller.appspotmail.com> wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 280d542f Merge tag 'drm-fixes-2021-03-05' of git://anongit..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=15ade5aed00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=952047a9dbff6a6a
> dashboard link: https://syzkaller.appspot.com/bug?extid=8fede7e30c7cee0de139
>
> Unfortunately, I don't have any reproducer for this issue yet.
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+8fede7e30c7cee0de139@syzkaller.appspotmail.com
#syz test: https://github.com/ming1/linux.git v5.12-block-test
next prev parent reply other threads:[~2021-03-22 8:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 11:08 [syzbot] KASAN: use-after-free Read in disk_part_iter_next (2) syzbot
2021-03-20 20:53 ` syzbot
2021-03-21 12:40 ` syzbot
2021-03-22 7:18 ` Christoph Hellwig
2021-03-22 7:49 ` Dmitry Vyukov
2021-03-22 8:01 ` syzbot
2021-03-22 22:21 ` Bart Van Assche
2021-03-24 9:49 ` Christoph Hellwig
2021-03-24 10:01 ` syzbot
2021-03-21 21:26 ` Bart Van Assche
2021-03-21 21:39 ` syzbot
2021-03-22 2:35 ` Ming Lei
2021-03-22 4:15 ` Bart Van Assche
2021-03-22 8:51 ` Ming Lei [this message]
2021-03-22 10:09 ` syzbot
2021-03-26 8:35 ` Ming Lei
2021-03-26 17:01 ` syzbot
2021-03-27 6:50 ` Ming Lei
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='CACVXFVO-6A_u-zNvkUt4x57gAwxJBDHx=Arc6KPKh560X3G29w@mail.gmail.com' \
--to=tom.leiming@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+8fede7e30c7cee0de139@syzkaller.appspotmail.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).