From: Luca Boccassi <bluca@debian.org>
To: SystemD Devel <systemd-devel@lists.freedesktop.org>,
"elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>,
binutils@sourceware.org, debhelper@packages.debian.org,
debian-dpkg@lists.debian.org, devel@lists.fedoraproject.org
Cc: "Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>,
"Lennart Poettering" <lennart@poettering.net>
Subject: Re: Storing package metadata in ELF objects
Date: Sat, 10 Apr 2021 13:38:31 +0100 [thread overview]
Message-ID: <2b91ec1654b6c07cca2b5c113df772c85c0dd22c.camel@debian.org> (raw)
In-Reply-To: <f9d47ea9fe3ce3a7e19573b64a64a8e3cc6a10b2.camel@debian.org>
[-- Attachment #1: Type: text/plain, Size: 2493 bytes --]
On Sat, 2021-04-10 at 13:29 +0100, Luca Boccassi wrote:
> Hello,
>
> Cross-posting to the mailing lists of a few relevant projects.
>
> After an initial discussion [0], recently we have been working on a new
> specification [0] to encode rich package-level metadata inside ELF
> objects, so that it can be included automatically in generated coredump
> files. The prototype to parse this in systemd-coredump and store the
> information in systemd-journal is ready for testing and merged
> upstream. We are now seeking further comments/opinions/suggestions, as
> we have a few months before the next release and thus there's plenty of
> time to make incompatible changes to the format and implementation, if
> required.
>
> A proposal to use this by default for all packages built in Fedora 35
> has been submitted [1].
>
> The Fedora Wiki and the systemd.io document have more details, but to
> make a long story short, a new .notes.package section with a JSON
> payload will be included in ELF objects, encoding various package-
> build-time information like distro name&version, package name&version,
> etc.
>
> To summarize from the discussion, the main reasons why we believe this
> is useful are as following:
>
> 1) minimal containers: the rpm database is not installed in the
> containers. The information about build-ids needs to be stored
> externally, so package name information is not available immediately,
> but only after offline processing. The new note doesn't depend on the
> rpm db in any way.
>
> 2) handling of a core from a container, where the container and host
> have different distros
>
> 3) self-built and external packages: unless a lot of care is taken to
> keep access to the debuginfo packages, this information may be lost.
> The new note is available even if the repository metadata gets lost.
> Users can easily provide equivalent information in a format that makes
> sense in their own environment. It should work even when rpms and debs
> and other formats are mixed, e.g. during container image creation.
>
> Other than in Fedora, we are already making the required code changes
> at Microsoft to use the same format&specification for internally-built
> binaries, and for tools that parse core files and logs.
>
> Tools for RPM and DEB (debhelper) integration are also available [3].
Wrong Fedora list address - off to a great start already :-)
(fixed now)
--
Kind regards,
Luca Boccassi
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-10 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 12:29 Luca Boccassi
2021-04-10 12:38 ` Luca Boccassi [this message]
2021-04-10 18:44 ` Zbigniew Jędrzejewski-Szmek
2021-04-30 17:57 ` Mark Wielaard
2021-05-04 13:43 ` Luca Boccassi
2021-05-06 1:17 ` Mark Wielaard
2021-05-06 11:43 ` Luca Boccassi
2021-05-14 10:41 ` Guillem Jover
2021-05-14 13:41 ` Luca Boccassi
2021-05-19 0:19 ` Guillem Jover
2021-05-19 14:58 ` Mark Wielaard
2021-05-24 10:17 ` Luca Boccassi
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=2b91ec1654b6c07cca2b5c113df772c85c0dd22c.camel@debian.org \
--to=bluca@debian.org \
--cc=binutils@sourceware.org \
--cc=debhelper@packages.debian.org \
--cc=debian-dpkg@lists.debian.org \
--cc=devel@lists.fedoraproject.org \
--cc=elfutils-devel@sourceware.org \
--cc=lennart@poettering.net \
--cc=systemd-devel@lists.freedesktop.org \
--cc=zbyszek@in.waw.pl \
/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).