From: Sean Christopherson <sean.j.christopherson@intel.com>
To: syzbot <syzbot+2e0179e5185bcd5b9440@syzkaller.appspotmail.com>
Cc: christoffer.dall@arm.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, maz@kernel.org,
pbonzini@redhat.com, peterx@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: slab-out-of-bounds Read in gfn_to_memslot
Date: Mon, 13 Apr 2020 20:20:12 -0700 [thread overview]
Message-ID: <20200414032011.GQ21204@linux.intel.com> (raw)
In-Reply-To: <000000000000f6ae4905a32a0633@google.com>
On Mon, Apr 13, 2020 at 04:03:04AM -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 36947254e5f981aeeedab1c7dfa35fc34d330e80
> Author: Sean Christopherson <sean.j.christopherson@intel.com>
> Date: Tue Feb 18 21:07:32 2020 +0000
>
> KVM: Dynamically size memslot array based on number of used slots
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1099775de00000
> start commit: 4f8a3cc1 Merge tag 'x86-urgent-2020-04-12' of git://git.ke..
> git tree: upstream
> final crash: https://syzkaller.appspot.com/x/report.txt?x=1299775de00000
> console output: https://syzkaller.appspot.com/x/log.txt?x=1499775de00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=3bfbde87e8e65624
> dashboard link: https://syzkaller.appspot.com/bug?extid=2e0179e5185bcd5b9440
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13e78c7de00000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14cf613fe00000
>
> Reported-by: syzbot+2e0179e5185bcd5b9440@syzkaller.appspotmail.com
> Fixes: 36947254e5f9 ("KVM: Dynamically size memslot array based on number of used slots")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
#syz dup: KASAN: slab-out-of-bounds Read in __kvm_gfn_to_hva_cache_init
prev parent reply other threads:[~2020-04-14 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-13 8:11 KASAN: slab-out-of-bounds Read in gfn_to_memslot syzbot
2020-04-13 11:03 ` syzbot
2020-04-14 3:20 ` 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=20200414032011.GQ21204@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=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=syzbot+2e0179e5185bcd5b9440@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.