linux-kernel - Re: [PATCH v7 2/9] arm64: report address tag when FEAT_MTE_TAGGED

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aEmg9cNGAzqsrTd1@e129823.arm.com>
Date: Wed, 11 Jun 2025 16:29:57 +0100
From: Yeoreum Yun <yeoreum.yun@....com>
To: Mark Brown <broonie@...nel.org>
Cc: catalin.marinas@....com, pcc@...gle.com, will@...nel.org,
	anshuman.khandual@....com, joey.gouly@....com,
	yury.khrustalev@....com, maz@...nel.org, oliver.upton@...ux.dev,
	frederic@...nel.org, akpm@...ux-foundation.org, surenb@...gle.com,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH v7 2/9] arm64: report address tag when
 FEAT_MTE_TAGGED_FAR is supported

Hi Mark.
> On Wed, Jun 11, 2025 at 02:58:11PM +0100, Yeoreum Yun wrote:
>
> >  	 * The architecture specifies that bits 63:60 of FAR_EL1 are UNKNOWN
> >  	 * for tag check faults. Set them to corresponding bits in the untagged
> > -	 * address.
> > +	 * address if ARM64_MTE_FAR isn't supported.
> > +	 * Otherwise, bits 63:60 of FAR_EL1 are KNOWN.
> >  	 */
>
> Should that be "are UNKNOWN"?

Otherwise in here mentions the case when ARM64_MTE_FAR is supported,
So the bits 63:60 of FAR_EL1 are "not UNKNOWN" but I write it with
KNOWN.
Do you want to change this to "not UNKNOWN"?
or Am I missing something?

--
Sincerely,
Yeoreum Yun