LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Will Deacon <will.deacon@arm.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
	ard.biesheuvel@linaro.org
Subject: [GIT PULL] arm64: fixes for -rc3
Date: Sun, 20 Jan 2019 00:04:22 +0000	[thread overview]
Message-ID: <20190120000420.GM26876@brain-police> (raw)

Hi Linus,

Please pull these three arm64 fixes for -rc3. We've plugged a couple of
nasty issues involving KASLR-enabled kernels, and removed a redundant
#define that was introduced as part of the KHWASAN fixes from akpm at -rc2.

The kernel.org servers wouldn't talk to me from NZ (the keys appeared to
have changed), so I ended up pushing via the UK which seems to have worked.
Please shout if anything looks weird.

Cheers,

Will

--->8

The following changes since commit 1c7fc5cbc33980acd13d668f1c8f0313d6ae9fd8:

  Linux 5.0-rc2 (2019-01-14 10:41:12 +1200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git tags/arm64-fixes

for you to fetch changes up to 7fa1e2e6afa7f4c9f46528e61de6a15d9e8dffd9:

  kasan, arm64: remove redundant ARCH_SLAB_MINALIGN define (2019-01-16 12:09:11 +0000)

----------------------------------------------------------------
arm64 fixes for -rc3

- Fix broken kpti page-table rewrite in bizarre KASLR configuration

- Fix module loading with KASLR

- Remove redundant definition of ARCH_SLAB_MINALIGN

----------------------------------------------------------------
Andrey Konovalov (1):
      kasan, arm64: remove redundant ARCH_SLAB_MINALIGN define

Ard Biesheuvel (1):
      arm64: kaslr: ensure randomized quantities are clean to the PoC

James Morse (1):
      arm64: kpti: Update arm64_kernel_use_ng_mappings() when forced on

 arch/arm64/include/asm/cache.h | 2 --
 arch/arm64/include/asm/mmu.h   | 5 ++++-
 arch/arm64/kernel/kaslr.c      | 8 ++++++--
 3 files changed, 10 insertions(+), 5 deletions(-)

             reply	other threads:[~2019-01-20  0:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-20  0:04 Will Deacon [this message]
2019-01-20  3:29 ` Linus Torvalds
2019-01-20  4:00 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2022-08-26 17:58 [GIT PULL] arm64 " Will Deacon
2022-08-26 19:09 ` pr-tracker-bot
2021-11-26 13:22 Will Deacon
2021-11-26 18:35 ` pr-tracker-bot
2021-07-22 15:55 Will Deacon
2021-07-22 18:00 ` pr-tracker-bot
2021-03-12 13:34 [GIT PULL] arm64: Fixes " Will Deacon
2021-03-12 20:03 ` pr-tracker-bot
2020-11-06 13:20 [GIT PULL] arm64 fixes " Will Deacon
2020-11-06 21:13 ` pr-tracker-bot
2020-06-26 13:21 Will Deacon
2020-06-27 16:00 ` pr-tracker-bot
2020-02-21 16:01 Will Deacon
2020-02-22  0:07 ` Linus Torvalds
2020-02-22  0:15 ` pr-tracker-bot
2019-10-09 13:30 [GIT PULL] arm64: Fixes " Will Deacon
2019-10-09 19:30 ` pr-tracker-bot
2019-05-30 16:11 [GIT PULL] arm64: fixes " Will Deacon
2019-05-31  4:25 ` pr-tracker-bot
2018-04-27 16:23 Will Deacon
2017-12-07 17:58 Will Deacon
2016-10-28 16:01 Will Deacon
2016-02-04 18:49 Will Deacon

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=20190120000420.GM26876@brain-police \
    --to=will.deacon@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: [GIT PULL] arm64: fixes for -rc3' \
    /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

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).