From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers@google.com>
Cc: tytso@mit.edu, stable@vger.kernel.org
Subject: Re: WTF: patch "[PATCH] fscrypto: don't use on-stack buffer for key derivation" was seriously submitted to be applied to the 4.8-stable tree?
Date: Mon, 21 Nov 2016 19:15:23 +0100 [thread overview]
Message-ID: <20161121181523.GA20389@kroah.com> (raw)
In-Reply-To: <20161121180120.GA28464@google.com>
On Mon, Nov 21, 2016 at 10:01:20AM -0800, Eric Biggers wrote:
> On Mon, Nov 21, 2016 at 01:39:02PM +0100, gregkh@linuxfoundation.org wrote:
> > The patch below was submitted to be applied to the 4.8-stable tree.
> >
> > I fail to see how this patch meets the stable kernel rules as found at
> > Documentation/stable_kernel_rules.txt.
> >
> > 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.
> >
> > thanks,
> >
> > greg k-h
> >
>
> Hi Greg,
>
> Indeed, as far as I'm concerned you should drop these two patches. They fix
> problems with virtually-mapped stacks which were added in 4.9, so there's no
> need to apply them to older kernels. I think Cc stable was left on by accident
> because the patches were originally going to wait until 4.10.
Ok, thanks, both now dropped.
greg k-h
prev parent reply other threads:[~2016-11-21 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 12:39 WTF: patch "[PATCH] fscrypto: don't use on-stack buffer for key derivation" was seriously submitted to be applied to the 4.8-stable tree? gregkh
2016-11-21 18:01 ` Eric Biggers
2016-11-21 18:15 ` 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=20161121181523.GA20389@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ebiggers@google.com \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.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