[PATCH] aarch64: MTE compatible strchrnul

H.J. Lu hjl.tools@gmail.com
Thu Jun 4 20:03:08 GMT 2020


On Thu, Jun 4, 2020 at 12:49 PM Szabolcs Nagy <nsz@port70.net> wrote:
>
> * H.J. Lu via Libc-alpha <libc-alpha@sourceware.org> [2020-06-04 05:04:23 -0700]:
> > On Wed, Jun 3, 2020 at 9:02 AM Andrea Corallo <andrea.corallo@arm.com> wrote:
> > > Adhemerval Zanella <adhemerval.zanella@linaro.org> writes:
> > > > Besides it the commit message does not give an overall description of
> > > > which changes it does to the generic implementation neither the requirements
> > > > of MTE support.
> > >
> > > I'll improve the commit message as suggested.  Regarding the MTE
> > > requirements given the function is backward compatible not sure what
> > > should be mentioned.
> > >
> >
> > My impression is if some object files aren't MTE compatible, you can't enable
> > MTE in the executable.  Is that correct?
>
> there can be code that is not mte compatible that would
> crash when memory tagging and tag checking are enabled.
> currently there is no object file marking for compatibility.
>
> i think we should mention in the commit message in what
> way the old code is incompatible with mte (e.g. it does
> out of bound loads that can go across a tag granule
> boundaries which can cause tag check failures with mte)

Should we add a marker to indicate that an object file is
mte compatible?

-- 
H.J.


More information about the Libc-alpha mailing list