From: Sean Christopherson <sean.j.christopherson@intel.com>
To: syzbot <syzbot+e06e0f40470ee2de4dda@syzkaller.appspotmail.com>
Cc: christoffer.dall@arm.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, pbonzini@redhat.com,
peterx@redhat.com, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in gfn_to_hva
Date: Fri, 10 Apr 2020 10:54:13 -0700 [thread overview]
Message-ID: <20200410175412.GF22482@linux.intel.com> (raw)
In-Reply-To: <00000000000095762005a2f25f4d@google.com>
On Fri, Apr 10, 2020 at 09:39:12AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 5d30bcac Merge tag '9p-for-5.7-2' of git://github.com/mart..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17243a9fe00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=2a7f60f3313b353e
> dashboard link: https://syzkaller.appspot.com/bug?extid=e06e0f40470ee2de4dda
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12b059afe00000
>
> The bug was bisected to:
>
> commit 5c0b4f3d5ccc2ced94b01c3256db1cf79dc95b81
> Author: Sean Christopherson <sean.j.christopherson@intel.com>
> Date: Tue Feb 18 21:07:26 2020 +0000
>
> KVM: Move memslot deletion to helper function
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13d14de7e00000
> final crash: https://syzkaller.appspot.com/x/report.txt?x=10314de7e00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=17d14de7e00000
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+e06e0f40470ee2de4dda@syzkaller.appspotmail.com
> Fixes: 5c0b4f3d5ccc ("KVM: Move memslot deletion to helper function")
#syz dup: KASAN: slab-out-of-bounds Read in __kvm_gfn_to_hva_cache_init
prev parent reply other threads:[~2020-04-10 17:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 16:39 KASAN: slab-out-of-bounds Read in gfn_to_hva syzbot
2020-04-10 17:54 ` Sean Christopherson [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=20200410175412.GF22482@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=christoffer.dall@arm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=syzbot+e06e0f40470ee2de4dda@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 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.