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, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: [GIT PULL] arm64 fixes for -rc7
Date: Fri, 23 Sep 2022 19:28:00 +0100	[thread overview]
Message-ID: <20220923182800.GA14450@willie-the-truck> (raw)

Hi Linus,

Please pull these arm64 fixes for -rc7. They're all very simple and
self-contained, although the CFI jump-table fix touches the generic
linker script as that's where the problematic macro lives.

Summary in the tag.

Cheers,

Will

--->8

The following changes since commit 3fe3fd5f30720b4afd3345cc186808125e7f5848:

  arm64: mm: fix resume for 52-bit enabled builds (2022-09-10 14:46:28 +0100)

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 13b0566962914e167cb3238fbe29ced618f07a27:

  vmlinux.lds.h: CFI: Reduce alignment of jump-table to function alignment (2022-09-23 13:39:01 +0100)

----------------------------------------------------------------
arm64 fixes for -rc7

- Fix false positive "sleeping while atomic" warning resulting from
  the kPTI rework taking a mutex too early.

- Fix possible overflow in AMU frequency calculation

- Fix incorrect shift in CMN PMU driver which causes problems with
  newer versions of the IP

- Reduce alignment of the CFI jump table to avoid huge kernel images
  and link errors with !4KiB page size configurations

----------------------------------------------------------------
Ilkka Koskinen (1):
      perf/arm-cmn: Add more bits to child node address offset field

Mark Rutland (1):
      arm64: mm: don't acquire mutex when rewriting swapper

Sergey Shtylyov (1):
      arm64: topology: fix possible overflow in amu_fie_setup()

Will Deacon (1):
      vmlinux.lds.h: CFI: Reduce alignment of jump-table to function alignment

 arch/arm64/kernel/topology.c      |  2 +-
 arch/arm64/mm/mmu.c               | 32 ++++++++++++++++++--------------
 drivers/perf/arm-cmn.c            |  2 +-
 include/asm-generic/vmlinux.lds.h |  3 +--
 4 files changed, 21 insertions(+), 18 deletions(-)

             reply	other threads:[~2022-09-23 18:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 18:28 Will Deacon [this message]
2022-09-23 22:43 ` [GIT PULL] arm64 fixes for -rc7 Linus Torvalds
2022-09-28 10:46   ` Mark Rutland
2022-09-23 22:53 ` pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2022-05-13 16:52 Will Deacon
2022-05-13 17:30 ` pr-tracker-bot
2021-08-20  8:53 Will Deacon
2021-08-20 20:09 ` pr-tracker-bot
2020-12-02 17:17 Will Deacon
2020-12-02 20:48 ` pr-tracker-bot
2020-03-20 15:35 Will Deacon
2020-03-20 17:15 ` pr-tracker-bot
2019-08-28 17:32 [GIT PULL] arm64: Fixes " Will Deacon
2019-08-28 17:45 ` pr-tracker-bot
2018-07-27 11:51 [GIT PULL] arm64: fixes " Will Deacon
2018-05-25 16:04 Will Deacon
2016-07-08 14: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=20220923182800.GA14450@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=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).