From: Greg KH <greg@kroah.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Voegtle <tv@lio96.de>,
stable@vger.kernel.org,
Zhuang Yanying <ann.zhuangyanying@huawei.com>,
LinFeng <linfeng23@huawei.com>
Subject: Re: proposing 7df003c85218b5f for v5.5.y, v5.4.y, 4.19.y, v4.14.y, v4.9.y
Date: Fri, 27 Mar 2020 08:54:53 +0100 [thread overview]
Message-ID: <20200327075453.GA1627266@kroah.com> (raw)
In-Reply-To: <8350b14e-f708-f2e3-19cd-4e85a4a3235c@redhat.com>
On Thu, Mar 26, 2020 at 07:04:15PM +0100, Paolo Bonzini wrote:
> On 26/03/20 18:43, Thomas Voegtle wrote:
> >
> > Hello,
> >
> > the following one line commit
> >
> > commit 7df003c85218b5f5b10a7f6418208f31e813f38f
> > Author: Zhuang Yanying <ann.zhuangyanying@huawei.com>
> > Date: Sat Oct 12 11:37:31 2019 +0800
> >
> > KVM: fix overflow of zero page refcount with ksm running
> >
> >
> > applies cleanly to v5.5.y, v5.4.y, 4.19.y, v4.14.y and v4.9.y.
> >
> > I actually ran into that bug on 4.9.y
> >
> > Thanks in advance,
> >
> > Thomas
> >
> >
> >
>
> Yes, indeed. It's not a trivial backport though, so I prefer to do it
> manually. I can help with that, or with reviews if Yanying already has
> patches ready.
Backports would be great, I'll wait for them before applying them.
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-27 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 17:43 proposing 7df003c85218b5f for v5.5.y, v5.4.y, 4.19.y, v4.14.y, v4.9.y Thomas Voegtle
2020-03-26 18:04 ` Paolo Bonzini
2020-03-26 20:08 ` Thomas Voegtle
2020-03-26 20:15 ` Paolo Bonzini
2020-03-27 7:54 ` Greg KH [this message]
2020-03-30 13:32 ` [PATCH 0/2] KVM: fix overflow of zero page refcount with ksm running Zhuang Yanying
2020-03-30 13:32 ` [PATCH 1/2] " Zhuang Yanying
2020-03-30 13:40 ` Greg KH
2020-03-30 13:32 ` [PATCH 2/2] KVM: special handling of zero_page in some flows Zhuang Yanying
2020-03-30 13:40 ` Greg KH
2020-03-30 13:40 ` [PATCH 0/2] KVM: fix overflow of zero page refcount with ksm running Greg KH
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=20200327075453.GA1627266@kroah.com \
--to=greg@kroah.com \
--cc=ann.zhuangyanying@huawei.com \
--cc=linfeng23@huawei.com \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tv@lio96.de \
/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.