From: Greg KH <greg@kroah.com>
To: Justin Forbes <jmforbes@linuxtx.org>
Cc: stable@vger.kernel.org, wang6495@umn.edu,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: virt: vbox: Only copy_from_user the request-header once
Date: Sun, 1 Jul 2018 16:54:12 +0200 [thread overview]
Message-ID: <20180701145412.GA8124@kroah.com> (raw)
In-Reply-To: <CAFxkdArGEV6E1GsfQHZFuw0fq+_DhzvMUgjVuC450i775K70-w@mail.gmail.com>
On Fri, Jun 22, 2018 at 01:28:50PM -0500, Justin Forbes wrote:
> I didn't see this one sent to stable, though it probably should be.
>
>
> commit bd23a7269834dc7c1f93e83535d16ebc44b75eba
> Author: Wenwen Wang <wang6495@umn.edu>
> Date: Tue May 8 08:50:28 2018 -0500
>
> virt: vbox: Only copy_from_user the request-header once
Good catch, now queued up, thanks.
greg k-h
prev parent reply other threads:[~2018-07-01 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 18:28 virt: vbox: Only copy_from_user the request-header once Justin Forbes
2018-07-01 14:54 ` 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=20180701145412.GA8124@kroah.com \
--to=greg@kroah.com \
--cc=hdegoede@redhat.com \
--cc=jmforbes@linuxtx.org \
--cc=stable@vger.kernel.org \
--cc=wang6495@umn.edu \
/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).