From: Matt Fleming <matt@codeblueprint.co.uk>
To: Greg KH <gregkh@linuxfoundation.org>
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 16:49:12 +0000 [thread overview]
Message-ID: <20160225164912.GC2772@codeblueprint.co.uk> (raw)
In-Reply-To: <20160225164158.GA22865@kroah.com>
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?
> thanks,
>
> greg k-h
>
> [1] Totally made up number, I think the true number is 100%, but maybe
> one or two patches have actually worked over the years. Most
> relevant example of this is some crypto patches that were "made
> simpler for stable" last week but were completely broken.
next prev parent reply other threads:[~2016-02-25 16:49 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 [this message]
2016-02-25 17:22 ` Greg KH
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=20160225164912.GC2772@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jlee@suse.com \
--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 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.