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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
 <GV1PR08MB10521255DDF2BE9AF745CEF7AFB812@GV1PR08MB10521.eurprd08.prod.outlook.com>
Date: Mon, 28 Apr 2025 15:46:17 +0000
From: Yeo Reum Yun <YeoReum.Yun@....com>
To: David Hildenbrand <david@...hat.com>, Catalin Marinas
	<Catalin.Marinas@....com>, "will@...nel.org" <will@...nel.org>,
	"broonie@...nel.org" <broonie@...nel.org>, Anshuman Khandual
	<Anshuman.Khandual@....com>, Joey Gouly <Joey.Gouly@....com>,
	"maz@...nel.org" <maz@...nel.org>, "oliver.upton@...ux.dev"
	<oliver.upton@...ux.dev>, "frederic@...nel.org" <frederic@...nel.org>, James
 Morse <James.Morse@....com>, "hardevsinh.palaniya@...iconsignals.io"
	<hardevsinh.palaniya@...iconsignals.io>,
	"shameerali.kolothum.thodi@...wei.com"
	<shameerali.kolothum.thodi@...wei.com>, "huangxiaojia2@...wei.com"
	<huangxiaojia2@...wei.com>, Mark Rutland <Mark.Rutland@....com>,
	"samuel.holland@...ive.com" <samuel.holland@...ive.com>,
	"palmer@...osinc.com" <palmer@...osinc.com>, "charlie@...osinc.com"
	<charlie@...osinc.com>, "thiago.bauermann@...aro.org"
	<thiago.bauermann@...aro.org>, "bgray@...ux.ibm.com" <bgray@...ux.ibm.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>, "puranjay@...nel.org"
	<puranjay@...nel.org>, "yang@...amperecomputing.com"
	<yang@...amperecomputing.com>, "mbenes@...e.cz" <mbenes@...e.cz>,
	"joel.granados@...nel.org" <joel.granados@...nel.org>
CC: "linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, nd <nd@....com>
Subject: Re: [PATCH v3 2/4] prtcl: introduce PR_MTE_STORE_ONLY

Hi David.

> > PR_MTE_STORE_ONLY is used to restrict the MTE tag check for store
> > opeartion only.
> >
> > Signed-off-by: Yeoreum Yun <yeoreum.yun@....com>
> > ---
> >   include/uapi/linux/prctl.h | 2 ++
> >   1 file changed, 2 insertions(+)
> >
> > diff --git a/include/uapi/linux/prctl.h b/include/uapi/linux/prctl.h
> > index 15c18ef4eb11..83ac566251d8 100644
> > --- a/include/uapi/linux/prctl.h
> > +++ b/include/uapi/linux/prctl.h
> > @@ -244,6 +244,8 @@ struct prctl_mm_map {
> >   # define PR_MTE_TAG_MASK            (0xffffUL << PR_MTE_TAG_SHIFT)
> >   /* Unused; kept only for source compatibility */
> >   # define PR_MTE_TCF_SHIFT           1
> > +/* MTE tag check store only */
> > +# define PR_MTE_STORE_ONLY           (1UL << 19)
>
> That is the next available bit after PR_MTE_TAG_MASK, correct?
>
> Would we want to leave some space to grow PR_MTE_TAG_MASK in the future
> (could that happen?)?

Yes it is. But I don't think it would grow up
since  GCR_EL1's exlude field size 16 bits where PR_MTE_TAG_MASK value is set
and the next bit is used by other purpose. 

thou, exclude field would be some bit filed in GCR_EL1
AFAIK there's no plan to add new exclude field to extend
and when new field is added for this, I think it would be better to add correspond
MASK for the new field.

Thanks.

---
Sincerely,
Yeoreum Yun

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ