mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>,
	Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: 王金浦 <jinpuwang@gmail.com>, LKML <linux-kernel@vger.kernel.org>,
	"KVM-ML (kvm@vger.kernel.org)" <kvm@vger.kernel.org>,
	x86@kernel.org
Subject: Re: VMs freezing when host is running 4.14
Date: Wed, 14 Feb 2018 11:23:44 +0100	[thread overview]
Message-ID: <62aa6b81-5456-07dc-cf64-e46747d3a70d@redhat.com> (raw)
In-Reply-To: <20180214020445.ebu4fhnmogqehunb@treble>

On 14/02/2018 03:04, Josh Poimboeuf wrote:
> On Sun, Feb 11, 2018 at 02:39:41PM +0100, Marc Haber wrote:
>> Hi,
>>
>> after in total nine weeks of bisecting, broken filesystems, service
>> outages (thankfully on unportant systems), 4.15 seems to have fixed the
>> issue. After going to 4.15, the crashes never happened again.
>>
>> They have, however, happened with each and every 4.14 release I tried,
>> which I stopped doing with 4.14.15 on Jan 28.
>>
>> This means, for me, that the issue is fixed and that I have just wasted
>> nine weeks of time.
>>
>> For you, this means that you have a crippling, data-eating issue in the
>> current long-term releae kernel. I do sincerely hope that I never have
>> to lay my eye on any 4.14 kernel and hope that no major distribution
>> will release with this version.
> 
> I saw something similar today, also in kvm_async_pf_task_wait().  I had
> -tip in the guest (based on 4.16.0-rc1) and Fedora
> 4.14.16-300.fc27.x86_64 on the host.

Hi Josh/Marc,

this is fixed by

    commit 2a266f23550be997d783f27e704b9b40c4010292
    Author: Haozhong Zhang <haozhong.zhang@intel.com>
    Date:   Wed Jan 10 21:44:42 2018 +0800

    KVM MMU: check pending exception before injecting APF
    
    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>
    Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

and it will be in 4.14.20.  Unfortunately I only heard about this issue
last week.

Thanks,

Paolo

      parent reply	other threads:[~2018-02-14 10:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 16:18 Marc Haber
2017-11-22  9:39 ` Marc Haber
2017-11-22 15:04   ` 王金浦
2017-11-22 15:52     ` Marc Haber
2017-11-22 16:43       ` Radim Krčmář
2017-11-23 15:20         ` Marc Haber
2017-11-23 15:59           ` Radim Krčmář
2017-11-23 16:18             ` Liran Alon
2017-11-23 16:24               ` Radim Krčmář
2017-11-23 16:26                 ` Liran Alon
2017-11-24  8:08                   ` Marc Haber
2017-12-01 14:43     ` Marc Haber
2018-01-08  9:10       ` Marc Haber
2018-02-11 13:39         ` Marc Haber
2018-02-14  2:04           ` Josh Poimboeuf
2018-02-14  2:56             ` Haozhong Zhang
2018-02-14  3:17               ` Josh Poimboeuf
2018-02-14 10:23             ` Paolo Bonzini [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=62aa6b81-5456-07dc-cf64-e46747d3a70d@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jinpuwang@gmail.com \
    --cc=jpoimboe@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mh+linux-kernel@zugschlus.de \
    --cc=x86@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

Powered by JetHome