Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>
Cc: mark.rutland@arm.com, kernel-team@android.com,
	Will Deacon <will@kernel.org>,
	Yury Khrustalev <yury.khrustalev@arm.com>
Subject: Re: [PATCH] arm64: mte: Fix PTRACE_{PEEK,POKE}MTETAGS error documentation
Date: Fri, 11 Sep 2026 14:44:08 +0100	[thread overview]
Message-ID: <178913101591.2459695.4180294828056716193.b4-ty@kernel.org> (raw)
In-Reply-To: <20260907113151.363924-1-catalin.marinas@arm.com>

On Mon, 07 Sep 2026 12:30:25 +0100, Catalin Marinas wrote:
> PTRACE_{PEEK,POKE}MTETAGS return -EIO rather than -EOPNOTSUPP (as
> documented) when no tags are copied from/to a mapping without PROT_MTE.
> This has been the behaviour since the interface was introduced, though
> the original intent was to distinguish between address not being
> accessible and mapped as untagged.
> 
> Update the documentation to match the implementation (de-facto ABI).
> Since -EOPNOTSUPP was never returned, change the error assignment to
> -EIO as well to avoid confusion.
> 
> [...]

Applied to arm64 (for-next/fixes), thanks!

[1/1] arm64: mte: Fix PTRACE_{PEEK,POKE}MTETAGS error documentation
      https://git.kernel.org/arm64/c/fdb9ebc7fb77

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev


      reply	other threads:[~2026-09-11 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 11:30 [PATCH] arm64: mte: Fix PTRACE_{PEEK,POKE}MTETAGS error documentation Catalin Marinas
2026-09-11 13:44 ` Will Deacon [this message]

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=178913101591.2459695.4180294828056716193.b4-ty@kernel.org \
    --to=will@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=yury.khrustalev@arm.com \
    /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