linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: torvalds@linux-foundation.org
Cc: catalin.marinas@arm.com, maz@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc2
Date: Fri, 16 Jul 2021 15:53:21 +0100	[thread overview]
Message-ID: <20210716145320.GB3161@willie-the-truck> (raw)

Hi Linus,

Please pull these arm64 fixes for -rc2. The bulk of the diffstat consists
of changes to our uaccess routines so that they fall back to bytewise
copying prior to reporting complete failure when the initial (multi-byte)
access faults. However, the most disappointing change here is that we've
had to bump ARCH_DMA_MINALIGN back to 128 bytes thanks to Qualcomm's "Kryo"
CPU, which ended up in the MSM8996 mobile SoC. Still, at least we're now
aware of this design and one of the hardware designers confirmed the
L2 cacheline size for us.

Cheers,

Will

--->8

The following changes since commit e73f0f0ee7541171d89f2e2491130c7771ba58d3:

  Linux 5.14-rc1 (2021-07-11 15:07:40 -0700)

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 e6f85cbeb23bd74b8966cf1f15bf7d01399ff625:

  arm64: entry: fix KCOV suppression (2021-07-15 17:37:55 +0100)

----------------------------------------------------------------
arm64 fixes for -rc2

- Fix instrumentation annotations for entry code

- Ensure kernel MTE state is restored correctly on resume from suspend

- Fix MTE fault from new strlen() routine

- Fallback to byte-wise accesses on initial uaccess fault

- Bump Clang requirement for BTI

- Revert ARCH_DMA_MINALIGN back to 128 bytes (shakes fist at Qualcomm)

----------------------------------------------------------------
Carlos Bilbao (1):
      arm64: Add missing header <asm/smp.h> in two files

Mark Rutland (4):
      arm64: fix strlen() with CONFIG_KASAN_HW_TAGS
      arm64: mte: fix restoration of GCR_EL1 from suspend
      arm64: entry: add missing noinstr
      arm64: entry: fix KCOV suppression

Nathan Chancellor (1):
      arm64: Restrict ARM64_BTI_KERNEL to clang 12.0.0 and newer

Robin Murphy (1):
      arm64: Avoid premature usercopy failure

Will Deacon (1):
      Revert "arm64: cache: Lower ARCH_DMA_MINALIGN to 64 (L1_CACHE_BYTES)"

 arch/arm64/Kconfig                |  3 ++-
 arch/arm64/include/asm/cache.h    |  2 +-
 arch/arm64/include/asm/smp_plat.h |  1 +
 arch/arm64/kernel/Makefile        |  2 +-
 arch/arm64/kernel/cpufeature.c    |  1 +
 arch/arm64/kernel/entry-common.c  |  2 +-
 arch/arm64/kernel/mte.c           | 15 ++-------------
 arch/arm64/lib/copy_from_user.S   | 13 ++++++++++---
 arch/arm64/lib/copy_in_user.S     | 21 ++++++++++++++-------
 arch/arm64/lib/copy_to_user.S     | 14 +++++++++++---
 arch/arm64/lib/strlen.S           | 10 ++++++++++
 11 files changed, 54 insertions(+), 30 deletions(-)

             reply	other threads:[~2021-07-16 14:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16 14:53 Will Deacon [this message]
2021-07-17  2:12 ` [GIT PULL] arm64 fixes for -rc2 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2022-04-08 16:29 Will Deacon
2022-04-08 17:46 ` pr-tracker-bot
2020-10-30 17:05 Will Deacon
2020-10-30 20:29 ` pr-tracker-bot
2020-06-19 12:43 Will Deacon
2020-06-19 19:30 ` pr-tracker-bot
2020-02-13 17:10 Will Deacon
2020-02-13 22:40 ` pr-tracker-bot
2019-07-26 13:12 [GIT PULL] arm64: " Will Deacon
2019-07-26 18:25 ` pr-tracker-bot
2019-01-11 18:20 Will Deacon
2019-01-11 20:40 ` pr-tracker-bot
2018-08-31 16:12 Will Deacon
2017-12-01 18:23 Will Deacon
2016-10-20 17:14 Will Deacon
2016-06-03 15:37 Will Deacon
2016-04-01 15:15 Will Deacon
2016-01-27 18:45 Will Deacon
2015-09-17 14:04 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=20210716145320.GB3161@willie-the-truck \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).