From: Bart Van Assche <bvanassche@acm.org>
To: Ming Lei <tom.leiming@gmail.com>
Cc: syzbot <syzbot+8fede7e30c7cee0de139@syzkaller.appspotmail.com>,
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, Hillf Danton <hdanton@sina.com>
Subject: Re: [syzbot] KASAN: use-after-free Read in disk_part_iter_next (2)
Date: Sun, 21 Mar 2021 21:15:56 -0700 [thread overview]
Message-ID: <954345c8-6010-71b5-a723-192cd1556d6d@acm.org> (raw)
In-Reply-To: <CACVXFVP0un7xv0_rZHV9d-jtDSSKpJcrFcmDsDiaj4j2CqV+DQ@mail.gmail.com>
On 3/21/21 7:35 PM, Ming Lei wrote:
> On Mon, Mar 22, 2021 at 7:03 AM Bart Van Assche <bvanassche@acm.org> wrote:
>>
>> On 3/14/21 4:08 AM, syzbot wrote:
>>> 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
>>
>> #syz test: https://github.com/bvanassche/linux a5f35387ebdc
>
> It should be the same issue which was addressed by
>
> aebf5db91705 block: fix use-after-free in disk_part_iter_next
>
> but converting to xarray introduced the issue again.
Hi Ming,
Since that patch does not re-apply cleanly, do you want to convert that
patch to the latest kernel version or do you perhaps expect me to do that?
Thanks,
Bart.
next prev parent reply other threads:[~2021-03-22 4:17 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 [this message]
2021-03-22 8:51 ` Ming Lei
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=954345c8-6010-71b5-a723-192cd1556d6d@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=hdanton@sina.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+8fede7e30c7cee0de139@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tom.leiming@gmail.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).