From: Greg KH <gregkh@linuxfoundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: stable@vger.kernel.org, nikola.ciprich@linuxbox.cz,
Haozhong Zhang <haozhong.zhang@intel.com>
Subject: Re: [PATCH] KVM MMU: check pending exception before injecting APF
Date: Fri, 9 Feb 2018 18:44:23 +0100 [thread overview]
Message-ID: <20180209174423.GB12761@kroah.com> (raw)
In-Reply-To: <577e399b-7ca8-3df0-e473-cbac9dbe122d@redhat.com>
On Fri, Feb 09, 2018 at 06:21:13PM +0100, Paolo Bonzini wrote:
> On 09/02/2018 18:17, Greg KH wrote:
> > On Fri, Feb 09, 2018 at 06:00:42PM +0100, Paolo Bonzini wrote:
> >> From: Haozhong Zhang <haozhong.zhang@intel.com>
> >>
> >> [ upstream commit 2a266f23550be997d783f27e704b9b40c4010292 Mon Sep 17 00:00:00 2001 ]
> >
> > Odd date :)
>
> Oops... git's fake mbox "From" line.
Yeah, I guessed, odd it showed up here...
> >> For example, when two APF's for page ready happen after one exit and
> >> the first one becomes pending, the second one will result in #DF.
> >> Instead, just handle the second page fault synchronously.
> >>
> >> Reported-by: Ross Zwisler <zwisler@gmail.com>
> >> Message-ID: <CAOxpaSUBf8QoOZQ1p4KfUp0jq76OKfGY4Uxs-Gg8ngReD99xww@mail.gmail.com>
> >> Reported-by: Alec Blayne <ab@tevsa.net>
> >> Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
> >> Fixes: 664f8e26b00c7673a8303b0d40853a0c24ca93e1
> >
> > So this is only needed for 4.14.y?
>
> Yes. 4.13 and 4.15 both work.
Wonderful, I'll queue this up after this round of kernels are released
in a few days.
thanks,
greg k-h
prev parent reply other threads:[~2018-02-09 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 17:00 [PATCH] KVM MMU: check pending exception before injecting APF Paolo Bonzini
2018-02-09 17:17 ` Greg KH
2018-02-09 17:21 ` Paolo Bonzini
2018-02-09 17:44 ` 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=20180209174423.GB12761@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=haozhong.zhang@intel.com \
--cc=nikola.ciprich@linuxbox.cz \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox