From: Greg KH <greg@kroah.com>
To: "Charles (Chas) Williams" <ciwillia@brocade.com>
Cc: stable@vger.kernel.org
Subject: Re: Please cherry-pick 06ce521af955 ("kvm: fix page struct leak in handle_vmon") to 4.9-stable
Date: Sun, 9 Apr 2017 21:20:39 +0200 [thread overview]
Message-ID: <20170409192039.GA28649@kroah.com> (raw)
In-Reply-To: <54fa6fb6-ef2f-eb66-6481-794457148c16@brocade.com>
On Thu, Apr 06, 2017 at 05:40:14PM -0400, Charles (Chas) Williams wrote:
> commit 06ce521af9558814b8606c0476c54497cf83a653 upstream.
>
> This addresses CVE-2017-2596.
Only 4.9? what about all other stable releases?
And any reason you didn't cc: the authors of the patch and the
maintainer?
thanks,
greg k-h
next prev parent reply other threads:[~2017-04-09 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 21:40 Please cherry-pick 06ce521af955 ("kvm: fix page struct leak in handle_vmon") to 4.9-stable Charles (Chas) Williams
2017-04-09 19:20 ` Greg KH [this message]
2017-04-10 14:37 ` Charles (Chas) Williams
2017-04-10 15:05 ` 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=20170409192039.GA28649@kroah.com \
--to=greg@kroah.com \
--cc=ciwillia@brocade.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;
as well as URLs for NNTP newsgroup(s).