stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: <stable@vger.kernel.org>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Peter Jones <pjones@redhat.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>, joeyli <jlee@suse.com>
Subject: Re: [PATCH 0/3] make efivarfs files immutable by default (for stable)
Date: Thu, 25 Feb 2016 17:22:14 +0000	[thread overview]
Message-ID: <20160225172137.GA23694@kroah.com> (raw)
In-Reply-To: <20160225164912.GC2772@codeblueprint.co.uk>

On Thu, Feb 25, 2016 at 04:49:12PM +0000, Matt Fleming wrote:
> On Thu, 25 Feb, at 04:41:59PM, Greg KH wrote:
> > On Thu, Feb 25, 2016 at 04:31:43PM +0000, Matt Fleming wrote:
> > > Stable folks,
> > > 
> > > This is a backport of the efivarfs anti-bricking changes [1] for
> > > stable. Some fixing up was required because the series doesn't
> > > include the ucs2 cleanups that are in Linus' tree since they're not
> > > really stable material.
> > 
> > What stable tree(s) do you want these applied to?
>  
> Probably as far as back v3.10, if possible. That was when efivarfs
> support was merged and had we known about this issue then, we would
> have had this immutable feature from day one.
> 
> > And if at all possible, I'd really prefer to take the original patches,
> > additional things and all, for stable kernels, as 95%[1] of the time
> > that we take "different" ones, there are bugs.
>  
> OK, gotcha.
> 
> > It also makes things easier for us to take additional changes later on
> > for other commits in the same area.  So can we just take the originals
> > please?
>  
> Sure, if that's what you'd prefer that's no problem. Would you like me
> to send a v2 series containing all the patches?

Yes, that would be great, or just a list of git commit ids if they all
apply just fine without any changes needed.

thanks,

greg k-h

  reply	other threads:[~2016-02-25 17:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 16:31 [PATCH 0/3] make efivarfs files immutable by default (for stable) Matt Fleming
2016-02-25 16:31 ` [PATCH 1/3] efi: Make our variable validation list include the guid Matt Fleming
2016-02-25 16:31 ` [PATCH 2/3] efi: Make efivarfs entries immutable by default Matt Fleming
2016-02-25 16:31 ` [PATCH 3/3] efi: Add pstore variables to the deletion whitelist Matt Fleming
2016-02-25 16:42 ` [PATCH 0/3] make efivarfs files immutable by default (for stable) Greg KH
2016-02-25 16:49   ` Matt Fleming
2016-02-25 17:22     ` Greg KH [this message]
2016-02-25 20:37       ` Matt Fleming

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=20160225172137.GA23694@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=jlee@suse.com \
    --cc=matt@codeblueprint.co.uk \
    --cc=mjg59@srcf.ucam.org \
    --cc=pjones@redhat.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).