All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: jgross@suse.com, stable@vger.kernel.org
Subject: Re: WTF: patch "[PATCH] x86/xen: allow userspace access during hypercalls" was seriously submitted to be applied to the 4.12-stable tree?
Date: Mon, 24 Jul 2017 17:13:11 -0700	[thread overview]
Message-ID: <20170725001311.GA14826@kroah.com> (raw)
In-Reply-To: <20170725000955.GG1095@mail-itl>

On Tue, Jul 25, 2017 at 02:09:55AM +0200, Marek Marczykowski-G�recki wrote:
> On Mon, Jul 24, 2017 at 04:45:02PM -0700, gregkh@linuxfoundation.org wrote:
> > The patch below was submitted to be applied to the 4.12-stable tree.
> > 
> > I fail to see how this patch meets the stable kernel rules as found at
> > Documentation/process/stable_kernel_rules.rst.
> > 
> > I could be totally wrong, and if so, please respond to 
> > <stable@vger.kernel.org> and let me know why this patch should be
> > applied.  Otherwise, it is now dropped from my patch queues, never to be
> > seen again.
> 
> This is a fix for -EFAULT on (any?) usage of /dev/xen/privcmd from
> inside of Xen HVM guest with SMAP enabled. Details in this thread:
> http://markmail.org/message/b6wxaipxbjyhiueg

Why wasn't that information in the changelog itself?  As it is it lookes
like a "here's a new feature" type of patch...

I'll go queue this up now, thanks.

greg k-h

      reply	other threads:[~2017-07-25  0:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 23:45 WTF: patch "[PATCH] x86/xen: allow userspace access during hypercalls" was seriously submitted to be applied to the 4.12-stable tree? gregkh
2017-07-25  0:09 ` Marek Marczykowski-Górecki
2017-07-25  0:13   ` 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=20170725001311.GA14826@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jgross@suse.com \
    --cc=marmarek@invisiblethingslab.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 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.