public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] efi/urgent for v5.14-rc6
Date: Sun, 15 Aug 2021 10:02:48 +0200	[thread overview]
Message-ID: <YRjKKLSZD5aN88W2@zn.tnic> (raw)

Hi Linus,

please pull the EFI accumulated pile of fixes (by way of Ard) for
v5.14-rc6.

Thx.

---

The following changes since commit ddab1e71d2df3513ed6029435b97dcd83fbaa372:

  Merge tag 'efi-urgent-for-v5.14-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi into efi/urgent (2021-07-20 13:30:14 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/efi_urgent_for_v5.14_rc6

for you to fetch changes up to 55203550f9afb027389bd24ce85bd90044c3aa81:

  Merge tag 'efi-urgent-for-v5.14-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi into efi/urgent (2021-08-10 10:24:49 +0200)

----------------------------------------------------------------
Ard says:

A batch of fixes for the arm64 stub image loader:

- fix a logic bug that can make the random page allocator fail
  spuriously
- force reallocation of the Image when it overlaps with firmware
  reserved memory regions
- fix an oversight that defeated on optimization introduced earlier
  where images loaded at a suitable offset are never moved if booting
  without randomization
- complain about images that were not loaded at the right offset by the
  firmware image loader.

----------------------------------------------------------------
Ard Biesheuvel (4):
      efi/libstub: arm64: Force Image reallocation if BSS was not reserved
      efi/libstub: arm64: Relax 2M alignment again for relocatable kernels
      efi/libstub: arm64: Warn when efi_random_alloc() fails
      efi/libstub: arm64: Double check image alignment at entry

Benjamin Herrenschmidt (1):
      arm64: efi: kaslr: Fix occasional random alloc (and boot) failure

Thomas Gleixner (1):
      Merge tag 'efi-urgent-for-v5.14-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi into efi/urgent

 drivers/firmware/efi/libstub/arm64-stub.c  | 71 +++++++++++++++++++++++++-----
 drivers/firmware/efi/libstub/randomalloc.c |  2 +
 2 files changed, 63 insertions(+), 10 deletions(-)

-- 
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg

             reply	other threads:[~2021-08-15  8:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-15  8:02 Borislav Petkov [this message]
2021-08-15 17:00 ` [GIT PULL] efi/urgent for v5.14-rc6 pr-tracker-bot

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=YRjKKLSZD5aN88W2@zn.tnic \
    --to=bp@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@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