From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Luca Boccassi <luca.boccassi@gmail.com>
Cc: mark@klomp.org, libc-alpha@sourceware.org
Subject: Re: [PATCH] elf: add definition for FDO_PACKAGING_METADATA note
Date: Mon, 22 Nov 2021 16:17:34 +0100 [thread overview]
Message-ID: <8735nousmp.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <81e0676d26e9f818b79ac31393e2ee613faf9db2.camel@gmail.com> (Luca Boccassi's message of "Mon, 22 Nov 2021 14:44:54 +0000")
* Luca Boccassi:
>> Do you have your own registry for this?
>
> Sorry, what do you mean by registry here? A public header? If so, then
> no we do not AFAIK.
A means for avoiding tag number collisions under the "FDO" namespace.
glibc <elf.h> only covers a small subset of the note section names. The
Solaris is probably not up to date, and we do not track FreeBSD and
NetBSD at all. (FreeBSD definitely has a bunch of their own tags.)
We can add it to our own <elf.h>, but the extension mechanism with its
namespace mechanism means that we don't have to.
Thanks,
Florian
next prev parent reply other threads:[~2021-11-22 15:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 19:39 [PATCH] elf: add definition for FDO_PACKAGING_METADATA note luca.boccassi--- via Libc-alpha
2021-11-22 14:03 ` Florian Weimer via Libc-alpha
2021-11-22 14:44 ` Luca Boccassi via Libc-alpha
2021-11-22 15:17 ` Florian Weimer via Libc-alpha [this message]
2021-11-23 9:42 ` Mark Wielaard
2021-11-26 16:49 ` Mark Wielaard
2021-11-26 17:01 ` Luca Boccassi via Libc-alpha
2021-11-26 17:01 ` [PATCH v2] elf: add definition for NT_FDO_PACKAGING_METADATA note luca.boccassi--- via Libc-alpha
2021-11-26 20:27 ` Florian Weimer via Libc-alpha
2021-11-26 20:59 ` Luca Boccassi via Libc-alpha
2021-11-26 20:58 ` [PATCH v3] elf: add definition for ELF_NOTE_FDO and " luca.boccassi--- via Libc-alpha
2021-11-29 20:35 ` Florian Weimer via Libc-alpha
2021-12-02 22:02 ` 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=8735nousmp.fsf@oldenburg.str.redhat.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=luca.boccassi@gmail.com \
--cc=mark@klomp.org \
/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).