From: Florian Weimer <fweimer@redhat.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] aarch64: MTE compatible strchrnul
Date: Wed, 03 Jun 2020 17:24:21 +0200 [thread overview]
Message-ID: <871rmwuq8q.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20200603151804.GG21536@arm.com> (Szabolcs Nagy's message of "Wed, 3 Jun 2020 16:18:05 +0100")
* Szabolcs Nagy:
> The 06/03/2020 17:04, Florian Weimer via Libc-alpha wrote:
>> * Adhemerval Zanella via Libc-alpha:
>>
>> > Afaiu there is no need to add any marking for MTE, the main difference
>> > it enforce 16-byte granularity read. I think you are confusing with
>> > BTI, which does require the GNU note.
>>
>> If there is no compatibility issue, then why are these changes to the
>> glibc string functions needed?
>>
>> Clearly I'm confused.
>
> string functions have problem (2): they assume that
> if an address is accessible then everything on that
> page is accessible via the same pointer (which
> is no longer true with mte).
Ahh.
> i think we can add the mte-safe string functions and
> tackle the abi compatibility issues separately:
I agree that markup is a separate issue.
Thanks,
Florian
next prev parent reply other threads:[~2020-06-03 15:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 9:43 Andrea Corallo
2020-06-03 11:27 ` Florian Weimer
2020-06-03 14:14 ` Andrea Corallo
2020-06-03 14:24 ` Florian Weimer
2020-06-03 14:33 ` Adhemerval Zanella
2020-06-03 14:53 ` Szabolcs Nagy
2020-06-03 15:03 ` Szabolcs Nagy
2020-06-03 15:04 ` Adhemerval Zanella
2020-06-03 15:04 ` Florian Weimer
2020-06-03 15:18 ` Szabolcs Nagy
2020-06-03 15:24 ` Florian Weimer [this message]
2020-06-03 14:40 ` Adhemerval Zanella
2020-06-03 16:01 ` Andrea Corallo
2020-06-04 12:04 ` H.J. Lu
2020-06-04 19:48 ` Szabolcs Nagy
2020-06-04 20:03 ` H.J. Lu
2020-06-05 7:38 ` Szabolcs Nagy
2020-06-05 8:45 ` Wilco Dijkstra
2020-06-05 16:25 ` Szabolcs Nagy
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=871rmwuq8q.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).