public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-efi@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	"H . Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, Dave Young <dyoung@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Pan Bian <bianpan2016@163.com>
Subject: Re: [GIT PULL 0/3] EFI fixes for v4.15
Date: Wed, 6 Dec 2017 18:20:19 +0100	[thread overview]
Message-ID: <20171206172019.j7rfcw32oloigul5@gmail.com> (raw)
In-Reply-To: <20171206095010.24170-1-ard.biesheuvel@linaro.org>


* Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:

> The following changes since commit ae64f9bd1d3621b5e60d7363bc20afb46aede215:
> 
>   Linux 4.15-rc2 (2017-12-03 11:01:47 -0500)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git efi-urgent
> 
> for you to fetch changes up to bfe89df500c99e29fbd0fd6f18e396f1625efcee:
> 
>   efi: add comment to avoid future expanding of sysfs systab (2017-12-05 18:11:36 +0000)
> 
> ----------------------------------------------------------------
> A couple of fixes for v4.15:
> - limit the permissions of EFI related sysfs nodes to 0400
> - use memunmap not kfree for a mapping created with memremap
> - add a comment to the code that produces the contents of
>   /sys/firmware/efi/systab that it already violates policy, and
>   no new entries should be added to it
> 
> ----------------------------------------------------------------
> Dave Young (1):
>       efi: add comment to avoid future expanding of sysfs systab
> 
> Greg Kroah-Hartman (1):
>       efi: move some sysfs files to be read-only by root
> 
> Pan Bian (1):
>       efi/esrt: use memunmap rather kfree to free the remapping
> 
>  drivers/firmware/efi/efi.c         |  5 +++--
>  drivers/firmware/efi/esrt.c        | 17 +++++++----------
>  drivers/firmware/efi/runtime-map.c | 10 +++++-----
>  include/linux/sysfs.h              |  6 ++++++
>  4 files changed, 21 insertions(+), 17 deletions(-)

Applied, thanks Ard!

	Ingo

      parent reply	other threads:[~2017-12-06 17:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06  9:50 [GIT PULL 0/3] EFI fixes for v4.15 Ard Biesheuvel
2017-12-06  9:50 ` [PATCH 1/3] efi: move some sysfs files to be read-only by root Ard Biesheuvel
2017-12-06 20:29   ` [tip:efi/urgent] efi: Move " tip-bot for Greg Kroah-Hartman
2017-12-06  9:50 ` [PATCH 2/3] efi/esrt: use memunmap rather kfree to free the remapping Ard Biesheuvel
2017-12-06 20:30   ` [tip:efi/urgent] efi/esrt: Use memunmap() instead of kfree() " tip-bot for Pan Bian
2017-12-06  9:50 ` [PATCH 3/3] efi: add comment to avoid future expanding of sysfs systab Ard Biesheuvel
2017-12-06 20:30   ` [tip:efi/urgent] efi: Add " tip-bot for Dave Young
2017-12-06 17:20 ` Ingo Molnar [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=20171206172019.j7rfcw32oloigul5@gmail.com \
    --to=mingo@kernel.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=bianpan2016@163.com \
    --cc=dyoung@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@codeblueprint.co.uk \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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