Linux-ARM-Kernel Archive on lore.kernel.org
 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,
	luis.machado@arm.com
Subject: [GIT PULL] arm64 fix for -rc5
Date: Fri, 29 Apr 2022 12:33:54 +0100	[thread overview]
Message-ID: <20220429113353.GA16032@willie-the-truck> (raw)

Hi Linus,

Please pull this fix to the MTE ELF ABI for a but that was added during
the most recent merge window as part of the coredump support. The issue
is that the value assigned to the new PT_ARM_MEMTAG_MTE segment type has
already been allocated to PT_AARCH64_UNWIND by the ELF ABI, so we've
bumped the value and changed the name of the identifier to be better
aligned with the existing one.

Cheers,

Will

--->8

The following changes since commit 23bc8f69f0eceecbb87c3801d2e48827d2dca92b:

  arm64: mm: fix p?d_leaf() (2022-04-22 11:28:36 +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 c35fe2a68f29a0bda15ae994154cacaae5f69791:

  elf: Fix the arm64 MTE ELF segment name and value (2022-04-28 11:37:06 +0100)

----------------------------------------------------------------
arm64 fix for -rc5

- Rename and reallocate the PT_ARM_MEMTAG_MTE ELF segment type

----------------------------------------------------------------
Catalin Marinas (1):
      elf: Fix the arm64 MTE ELF segment name and value

 Documentation/arm64/memory-tagging-extension.rst | 4 ++--
 arch/arm64/kernel/elfcore.c                      | 2 +-
 include/uapi/linux/elf.h                         | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2022-04-29 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 11:33 Will Deacon [this message]
2022-04-29 17:47 ` [GIT PULL] arm64 fix for -rc5 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2016-11-07 17:57 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=20220429113353.GA16032@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=luis.machado@arm.com \
    --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