From: Yann Sionneau <ysionneau@kalray.eu>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-kernel@vger.kernel.org, Eric Paris <eparis@redhat.com>,
linux-mm@kvack.org, linux-audit@redhat.com,
Clement Leger <clement.leger@bootlin.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [RFC PATCH 02/25] kvx: Add ELF-related definitions
Date: Wed, 18 Jan 2023 09:48:03 +0100 [thread overview]
Message-ID: <eaba8723-606b-4f77-c647-afb3071f7496@kalray.eu> (raw)
In-Reply-To: <875ydnmhcv.fsf@email.froward.int.ebiederm.org>
On 03/01/2023 22:35, Eric W. Biederman wrote:
> Yann Sionneau <ysionneau@kalray.eu> writes:
>
>> Add ELF-related definitions for kvx, including: EM_KVX,
>> AUDIT_ARCH_KVX and NT_KVX_TCA.
> Has someone written an SYSVABI architecture specification for
> your architecture?
Internally at Kalray we have an ABI document, I started a discussion
about its publication.
It will not be part of the V2, but I'm working on it.
>
> I feel uncomfortable with the linux-kernel headers being the
> authoritative place for the ELF abi definitions.
>
> Especially since the linux kernel does not deal with relocations,
> and the kernel headers could diverge from the real world and no one
> would notice..
>
> I know at least at one point the linux standards base was taking
> up the work on collecting up some of these definitions. I would
> be happy if there was anything outside of the linux kernel that
> people could refer too.
I completely agree with you!
Thanks for the review.
--
Yann
--
Linux-audit mailing list
Linux-audit@redhat.com
https://listman.redhat.com/mailman/listinfo/linux-audit
next prev parent reply other threads:[~2023-01-18 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 16:43 [RFC PATCH 00/25] Upstream kvx Linux port Yann Sionneau
2023-01-03 16:43 ` [RFC PATCH 02/25] kvx: Add ELF-related definitions Yann Sionneau
2023-01-03 21:35 ` Eric W. Biederman
2023-01-18 8:48 ` Yann Sionneau [this message]
2023-01-03 20:52 ` [RFC PATCH 00/25] Upstream kvx Linux port Rob Herring
2023-01-04 15:58 ` Arnd Bergmann
2023-01-05 10:40 ` Jules Maselbas
2023-01-05 12:05 ` Arnd Bergmann
2023-01-05 14:12 ` Steven Rostedt
2023-01-07 6:25 ` Jeff Xie
2023-01-09 13:21 ` Yann Sionneau
2023-01-09 15:11 ` Jeff Xie
[not found] ` <bccad498-3af2-08f1-8264-cf7b438732d3@kalray.eu>
[not found] ` <CAEr6+EC0SCXLrQ2YNYyCyMK1Z9=3=ajbbLP+RKSsARGsmJO9YA@mail.gmail.com>
2023-01-16 7:31 ` Jeff Xie
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=eaba8723-606b-4f77-c647-afb3071f7496@kalray.eu \
--to=ysionneau@kalray.eu \
--cc=clement.leger@bootlin.com \
--cc=ebiederm@xmission.com \
--cc=eparis@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).