From: Szabolcs Nagy via Libc-alpha <libc-alpha@sourceware.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH v6 1/1] <sys/tagged-address.h>: An API for tagged address
Date: Fri, 3 Sep 2021 10:12:33 +0100 [thread overview]
Message-ID: <20210903091231.GC21740@arm.com> (raw)
In-Reply-To: <CAMe9rOoLwn54Q9VYcZb-S4WT7n03Ze9995haBxTu2LXy_wAkNQ@mail.gmail.com>
The 08/23/2021 07:15, H.J. Lu via Libc-alpha wrote:
> On Mon, Aug 23, 2021 at 6:49 AM Florian Weimer <fweimer@redhat.com> wrote:
> > * H. J. Lu:
> > > On Mon, Aug 23, 2021 at 2:28 AM Florian Weimer <fweimer@redhat.com> wrote:
> > >> As a side effect of the libpthread merge, we freed DF_1_INITFIRST for
> > >> other uses, so you should be able to work around initialization ordering
> > >> issues, too.
> > >
> > > The issue here is that LAM should only be enabled ONCE before main
> > > and thread creation. Neither DF_1_INITFIRST nor kernel API can properly
> > > enforce it.
> >
> > How does AArch64 solve this? Different kernel API?
>
> I don't think that AArch64 has addressed this issue at all.
i expect the hwasan runtime to have an initializer that
ensures that it runs once, early (e.g. the shadow map
has to be set up very early too: before any instrumented
user code may run)
is there a reason the lam setup cannot use this mechanism?
next prev parent reply other threads:[~2021-09-03 9:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 12:45 [PATCH v6 0/1] RFC: Add <sys/tagged-address.h> H.J. Lu via Libc-alpha
2021-08-22 12:45 ` [PATCH v6 1/1] <sys/tagged-address.h>: An API for tagged address H.J. Lu via Libc-alpha
2021-08-23 9:28 ` Florian Weimer via Libc-alpha
2021-08-23 13:40 ` H.J. Lu via Libc-alpha
2021-08-23 13:49 ` Florian Weimer via Libc-alpha
2021-08-23 14:15 ` H.J. Lu via Libc-alpha
2021-09-03 9:12 ` Szabolcs Nagy via Libc-alpha [this message]
2021-09-03 13:58 ` H.J. Lu via Libc-alpha
2021-09-06 8:52 ` Florian Weimer via Libc-alpha
2021-09-06 13:34 ` H.J. Lu via Libc-alpha
2021-09-17 10:19 ` Florian Weimer via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210903091231.GC21740@arm.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.com \
--cc=kirill.shutemov@linux.intel.com \
--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).