linux-kernel.vger.kernel.org archive mirror
 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 5.11-rc5
Date: Fri, 22 Jan 2021 19:07:21 +0000	[thread overview]
Message-ID: <20210122190719.GA29705@gaia> (raw)

Hi Linus,

Please pull the arm64 fixes below. Thanks.

The following changes since commit 3a57a643a851dbb1c4a1819394ca009e3bfa4813:

  arm64: selftests: Fix spelling of 'Mismatch' (2021-01-15 10:05:27 +0000)

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 75bd4bff300b3c5252d4a0e7a959569c62d1dbae:

  arm64: kprobes: Fix Uexpected kernel BRK exception at EL1 (2021-01-22 16:05:29 +0000)

----------------------------------------------------------------
arm64 fixes:

- Correctly mask out bits 63:60 in a kernel tag check fault address
  (specified as unknown by the architecture). Previously they were just
  zeroed but for kernel pointers they need to be all ones.

- Fix a panic (unexpected kernel BRK exception) caused by kprobes being
  reentered due to an interrupt.

----------------------------------------------------------------
Andrey Konovalov (1):
      kasan, arm64: fix pointer tags in KASAN reports

Qais Yousef (1):
      arm64: kprobes: Fix Uexpected kernel BRK exception at EL1

 arch/arm64/kernel/probes/kprobes.c | 4 ++--
 arch/arm64/mm/fault.c              | 7 ++++---
 2 files changed, 6 insertions(+), 5 deletions(-)

-- 
Catalin

             reply	other threads:[~2021-01-22 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 19:07 Catalin Marinas [this message]
2021-01-22 22:00 ` [GIT PULL] arm64 fixes for 5.11-rc5 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=20210122190719.GA29705@gaia \
    --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;
as well as URLs for NNTP newsgroup(s).