public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] arm64 fixes for 6.13-rc2
Date: Fri, 6 Dec 2024 18:27:33 +0000	[thread overview]
Message-ID: <Z1NCFeR4iBm5Bxqg@arm.com> (raw)

Hi Linus,

Please pull the arm64 fixes below. Nothing major, some left-overs from
the recent merging window (MTE, coco) and some newly found issues like
the ptrace() ones. More details in the tag. Thanks.

The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:

  Linux 6.13-rc1 (2024-12-01 14:28:56 -0800)

are available in the Git repository at:

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

for you to fetch changes up to d60624f72d15862a96965b945f6ddfee9a1359e7:

  arm64: ptrace: fix partial SETREGSET for NT_ARM_GCS (2024-12-05 18:05:51 +0000)

----------------------------------------------------------------
arm64 fixes for 6.13-rc2:

- MTE/hugetlbfs:

  - Set VM_MTE_ALLOWED in the arch code and remove it from the core code
    for hugetlbfs mappings

  - Fix copy_highpage() warning when the source is a huge page but not
    MTE tagged, taking the wrong small page path

- drivers/virt/coco:

  - Add the pKVM and Arm CCA drivers under the arm64 maintainership

  - Fix the pkvm driver to fall back to ioremap() (and warn) if the
    MMIO_GUARD hypercall fails

  - Keep the Arm CCA driver default 'n' rather than 'm'

- A series of fixes for the arm64 ptrace() implementation, potentially
  leading to the kernel consuming uninitialised stack variables when
  PTRACE_SETREGSET is invoked with a length of 0

- Fix zone_dma_limit calculation when RAM starts below 4GB and ZONE_DMA
  is capped to this limit

- Fix early boot warning with CONFIG_DEBUG_VIRTUAL=y triggered by a call
  to page_to_phys() (from patch_map()) which checks pfn_valid() before
  vmemmap has been set up

- Do not clobber bits 15:8 of the ASID used for TTBR1_EL1 and TLBI ops
  when the kernel assumes 8-bit ASIDs but running under a hypervisor on
  a system that implements 16-bit ASIDs (found running Linux under
  Parallels on Apple M4)

- ACPI/IORT: Add PMCG platform information for HiSilicon HIP09A as it is
  using the same SMMU PMCG as HIP09 and suffers from the same errata

- Add GCS to cpucap_is_possible(), missed in the recent merge

----------------------------------------------------------------
Catalin Marinas (2):
      arm64: Ensure bits ASID[15:8] are masked out when the kernel uses 8-bit ASIDs
      arm64: mte: Fix copy_highpage() warning on hugetlb folios

Mark Rutland (5):
      arm64: patching: avoid early page_to_phys()
      arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL
      arm64: ptrace: fix partial SETREGSET for NT_ARM_FPMR
      arm64: ptrace: fix partial SETREGSET for NT_ARM_POE
      arm64: ptrace: fix partial SETREGSET for NT_ARM_GCS

Qinxin Xia (1):
      ACPI/IORT: Add PMCG platform information for HiSilicon HIP09A

Robin Murphy (1):
      arm64: cpufeature: Add GCS to cpucap_is_possible()

Suzuki K Poulose (1):
      coco: virt: arm64: Do not enable cca guest driver by default

Will Deacon (2):
      drivers/virt: pkvm: Don't fail ioremap() call if MMIO_GUARD fails
      MAINTAINERS: Add CCA and pKVM CoCO guest support to the ARM64 entry

Yang Shi (2):
      arm64: mte: set VM_MTE_ALLOWED for hugetlbfs at correct place
      arm64: mm: Fix zone_dma_limit calculation

 Documentation/arch/arm64/silicon-errata.rst   |  5 ++--
 MAINTAINERS                                   |  2 ++
 arch/arm64/include/asm/cpucaps.h              |  2 ++
 arch/arm64/include/asm/cpufeature.h           |  3 +--
 arch/arm64/include/asm/mman.h                 |  3 ++-
 arch/arm64/kernel/patching.c                  | 21 +++++++---------
 arch/arm64/kernel/ptrace.c                    | 36 +++++++++++++++++++++------
 arch/arm64/mm/context.c                       |  4 +--
 arch/arm64/mm/copypage.c                      |  8 +++---
 arch/arm64/mm/init.c                          | 17 ++++++-------
 drivers/acpi/arm64/iort.c                     |  2 ++
 drivers/virt/coco/arm-cca-guest/Kconfig       |  1 -
 drivers/virt/coco/pkvm-guest/arm-pkvm-guest.c |  6 +----
 fs/hugetlbfs/inode.c                          |  2 +-
 14 files changed, 67 insertions(+), 45 deletions(-)

-- 
Catalin

             reply	other threads:[~2024-12-06 18:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 18:27 Catalin Marinas [this message]
2024-12-06 22:01 ` [GIT PULL] arm64 fixes for 6.13-rc2 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=Z1NCFeR4iBm5Bxqg@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=will@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