From: Jason Wang <jasowang@redhat.com>
To: syzbot <syzbot+8267e9af795434ffadad@syzkaller.appspotmail.com>,
aarcange@redhat.com, davem@davemloft.net, hch@infradead.org,
james.bottomley@hansenpartnership.com, jglisse@redhat.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-parisc@vger.kernel.org, mst@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Write in tlb_finish_mmu
Date: Wed, 24 Jul 2019 15:07:35 +0800 [thread overview]
Message-ID: <e003d427-36ef-a6bc-e433-36d90080e3cb@redhat.com> (raw)
In-Reply-To: <0000000000002c183d058e0e3abd@google.com>
On 2019/7/20 上午4:04, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 7f466032dc9e5a61217f22ea34b2df932786bbfc
> Author: Jason Wang <jasowang@redhat.com>
> Date: Fri May 24 08:12:18 2019 +0000
>
> vhost: access vq metadata through kernel virtual address
>
> bisection log:
> https://syzkaller.appspot.com/x/bisect.txt?x=11642a58600000
> start commit: 22051d9c Merge tag 'platform-drivers-x86-v5.3-2' of
> git://..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=13642a58600000
> console output: https://syzkaller.appspot.com/x/log.txt?x=15642a58600000
> kernel config: https://syzkaller.appspot.com/x/.config?x=d831b9cbe82e79e4
> dashboard link:
> https://syzkaller.appspot.com/bug?extid=8267e9af795434ffadad
> userspace arch: i386
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10d58784600000
>
> Reported-by: syzbot+8267e9af795434ffadad@syzkaller.appspotmail.com
> Fixes: 7f466032dc9e ("vhost: access vq metadata through kernel virtual
> address")
>
> For information about bisection process see:
> https://goo.gl/tpsmEJ#bisection
#syz dup: WARNING in __mmdrop
prev parent reply other threads:[~2019-07-24 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000045e7a1058e02458a@google.com>
2019-07-19 20:04 ` KASAN: use-after-free Write in tlb_finish_mmu syzbot
2019-07-24 7:07 ` Jason Wang [this message]
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=e003d427-36ef-a6bc-e433-36d90080e3cb@redhat.com \
--to=jasowang@redhat.com \
--cc=aarcange@redhat.com \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=jglisse@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mst@redhat.com \
--cc=syzbot+8267e9af795434ffadad@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).