From: Greg KH <gregkh@linuxfoundation.org>
To: Zubin Mithra <zsm@chromium.org>
Cc: stable@vger.kernel.org, groeck@chromium.org, kernellwp@gmail.com,
tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com
Subject: Re: bbeac2830f4d ("KVM: X86: Fix residual mmio emulation request to userspace")
Date: Fri, 22 Mar 2019 12:07:15 +0100 [thread overview]
Message-ID: <20190322110715.GC11649@kroah.com> (raw)
In-Reply-To: <20190321213737.GA181869@google.com>
On Thu, Mar 21, 2019 at 02:37:39PM -0700, Zubin Mithra wrote:
> Hello,
>
> Syzkaller has triggered a warning when fuzzing a 4.4 kernel with the following stacktrace.
> Call Trace:
> [<ffffffff819a9933>] __dump_stack lib/dump_stack.c:15 [inline]
> [<ffffffff819a9933>] dump_stack+0xba/0x10e lib/dump_stack.c:51
> [<ffffffff813c8bdc>] panic+0x1c4/0x389 kernel/panic.c:116
> [<ffffffff811c654c>] __warn+0x175/0x1be kernel/panic.c:470
> [<ffffffff813c8dde>] warn_slowpath_null+0x3d/0x42 kernel/panic.c:514
> [<ffffffff81046295>] kvm_arch_vcpu_ioctl_run+0x2ce/0x35a3 arch/x86/kvm/x86.c:6896
> [<ffffffff8100d5b8>] kvm_vcpu_ioctl+0x37f/0xa83 arch/x86/kvm/../../../virt/kvm/kvm_main.c:2437
> [<ffffffff814ab3f9>] vfs_ioctl fs/ioctl.c:43 [inline]
> [<ffffffff814ab3f9>] do_vfs_ioctl+0xcb6/0xd15 fs/ioctl.c:630
> [<ffffffff814ab4c5>] SYSC_ioctl fs/ioctl.c:645 [inline]
> [<ffffffff814ab4c5>] SyS_ioctl+0x6d/0xa8 fs/ioctl.c:636
> [<ffffffff83328c3a>] entry_SYSCALL_64_fastpath+0x31/0xb3
>
> Could the following patch be applied to v4.4.y and 4.9.y?
> * bbeac2830f4d ("KVM: X86: Fix residual mmio emulation request to userspace")
>
> Tests run:
> * Chrome OS tryjobs
> * Syzkaller reproducer
Now queued up, thanks!
greg k-h
prev parent reply other threads:[~2019-03-22 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 21:37 bbeac2830f4d ("KVM: X86: Fix residual mmio emulation request to userspace") Zubin Mithra
2019-03-22 11:07 ` Greg KH [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=20190322110715.GC11649@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=groeck@chromium.org \
--cc=hpa@zytor.com \
--cc=kernellwp@gmail.com \
--cc=mingo@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=zsm@chromium.org \
/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.