From: Luis Henriques <luis.henriques@canonical.com>
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/7] make efivarfs files immutable by default (for 3.10 and 3.14)
Date: Tue, 15 Mar 2016 14:23:28 +0000 [thread overview]
Message-ID: <20160315142328.GD3208@ares> (raw)
In-Reply-To: <1457618751-11514-1-git-send-email-matt@codeblueprint.co.uk>
On Thu, Mar 10, 2016 at 02:05:44PM +0000, Matt Fleming wrote:
> This is a backport of the patches previously sent for stable here,
>
> http://article.gmane.org/gmane.linux.kernel.stable/166813
>
> This series applies to 3.10-stable and 3.14-stable as Greg reported
> that the original stable patches didn't apply cleanly.
>
Thank you, Matt. I'm also picking these commits to the 3.16 kernel,
basing the backports on these ones.
Cheers,
--
Lu�s
> Jason Andryuk (1):
> lib/ucs2_string: Correct ucs2 -> utf8 conversion
>
> Matt Fleming (2):
> efi: Do variable name validation tests in utf8
> efi: Add pstore variables to the deletion whitelist
>
> Peter Jones (4):
> lib/ucs2_string: Add ucs2 -> utf8 helper functions
> efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version
> efi: Make our variable validation list include the guid
> efi: Make efivarfs entries immutable by default
>
> Documentation/filesystems/efivarfs.txt | 7 ++
> drivers/firmware/efi/efivars.c | 34 +++--
> drivers/firmware/efi/vars.c | 164 +++++++++++++++++--------
> fs/efivarfs/file.c | 71 +++++++++++
> fs/efivarfs/inode.c | 30 +++--
> fs/efivarfs/internal.h | 3 +-
> fs/efivarfs/super.c | 16 ++-
> include/linux/efi.h | 9 +-
> include/linux/ucs2_string.h | 4 +
> lib/ucs2_string.c | 62 ++++++++++
> tools/testing/selftests/efivarfs/efivarfs.sh | 19 ++-
> tools/testing/selftests/efivarfs/open-unlink.c | 72 ++++++++++-
> 12 files changed, 398 insertions(+), 93 deletions(-)
>
> --
> 2.6.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe stable" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-03-15 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 14:05 [PATCH 0/7] make efivarfs files immutable by default (for 3.10 and 3.14) Matt Fleming
2016-03-10 14:05 ` [PATCH 1/7] lib/ucs2_string: Add ucs2 -> utf8 helper functions Matt Fleming
2016-03-10 14:05 ` [PATCH 2/7] efi: Use ucs2_as_utf8 in efivarfs instead of open coding a bad version Matt Fleming
2016-03-10 14:05 ` [PATCH 3/7] efi: Do variable name validation tests in utf8 Matt Fleming
2016-03-10 14:05 ` [PATCH 4/7] efi: Make our variable validation list include the guid Matt Fleming
2016-03-10 14:05 ` [PATCH 5/7] efi: Make efivarfs entries immutable by default Matt Fleming
2016-03-10 14:05 ` [PATCH 6/7] efi: Add pstore variables to the deletion whitelist Matt Fleming
2016-03-10 14:05 ` [PATCH 7/7] lib/ucs2_string: Correct ucs2 -> utf8 conversion Matt Fleming
2016-03-13 4:00 ` [PATCH 0/7] make efivarfs files immutable by default (for 3.10 and 3.14) Greg KH
2016-03-15 14:23 ` Luis Henriques [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=20160315142328.GD3208@ares \
--to=luis.henriques@canonical.com \
--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