All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.de>,
	stable@vger.kernel.org
Subject: Re: 4.14.x - KVM guests crashing
Date: Thu, 15 Feb 2018 08:53:03 +0100	[thread overview]
Message-ID: <20180215075303.GA4331@kroah.com> (raw)
In-Reply-To: <20180213155921.GG5021@pcnci.linuxbox.cz>

On Tue, Feb 13, 2018 at 04:59:21PM +0100, Nikola Ciprich wrote:
> > > it's been introduced by 4.14 and seems to be fixed by
> > > 2a266f23550be997d783f27e704b9b40c4010292 (no crash with it applied so 
> > > far for me). Greg already has it queued for next 4.14.x release.
> > 
> > I do?  I don't see it in my queue anywhere.  Are you sure I've applied
> > it?
> 
> hmm, you've confirmed you'll queue it up on 9th of Feb:
> https://www.spinics.net/lists/stable/msg214724.html
> 
> I've been testing 4.14.18 with that one on top since then (it's rock solid
> now) and thought it got into the queue then.. my bad, sorry
> about confusion..

Ugh, nevermind, I already queued this up.

Too many patches floating around right now, the merge window is the
worst for stable patches...

greg k-h

  reply	other threads:[~2018-02-15  7:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09  9:56 4.14.x - KVM guests crashing Nikola Ciprich
2018-02-09 13:06 ` Greg KH
2018-02-09 13:10   ` Nikola Ciprich
2018-02-10 21:52   ` Christoph Biedl
2018-02-11  7:25     ` Nikola Ciprich
2018-02-13 15:43       ` Greg KH
2018-02-13 15:59         ` Nikola Ciprich
2018-02-15  7:53           ` Greg KH [this message]
2018-02-14 22:29       ` Christoph Biedl

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=20180215075303.GA4331@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel.bfrz@manchmal.in-ulm.de \
    --cc=nikola.ciprich@linuxbox.cz \
    --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 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.