From: Hajime Tazaki <thehajime@gmail.com>
To: ebiederm@xmission.com
Cc: linux-um@lists.infradead.org, ricarkol@google.com,
Liam.Howlett@oracle.com, kees@kernel.org,
viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v5 02/13] x86/um: nommu: elf loader for fdpic
Date: Sat, 14 Dec 2024 07:21:35 +0900 [thread overview]
Message-ID: <m2o71f5imo.wl-thehajime@gmail.com> (raw)
In-Reply-To: <87r06bz1uf.fsf@email.froward.int.ebiederm.org>
On Sat, 14 Dec 2024 06:53:44 +0900,
Eric W. Biederman wrote:
> > config BINFMT_ELF
> > bool "Kernel support for ELF binaries"
> > - depends on MMU
> > select ELFCORE
> > default y
> > help
> > @@ -58,7 +57,7 @@ config ARCH_USE_GNU_PROPERTY
> > config BINFMT_ELF_FDPIC
> > bool "Kernel support for FDPIC ELF binaries"
> > default y if !BINFMT_ELF
> > - depends on ARM || ((M68K || RISCV || SUPERH || UML || XTENSA) && !MMU)
> > + depends on ARM || ((M68K || RISCV || SUPERH || XTENSA) && !MMU)
> > select ELFCORE
> > help
> > ELF FDPIC binaries are based on ELF, but allow the individual load
>
> You have my apologies I was most definitely confused. BINFMT_ELF
> currently does not work without an MMU.
no problem.
> >> I just react a little strongly to the assertion that elf_fdpic is
> >> the only path when I don't see why that should be.
> >>
> >> Especially for an architecture like user-mode-linux where I would expect
> >> it to run the existing binaries for a port.
> >
> > I understand your concern, and will try to work on improving this
> > situation a bit.
> >
> > Another naive question: are there any past attempts to do the similar
> > thing (binfmt_elf without MMU) ?
>
> At this point what I would recommend is:
>
> Merge your original patch. Get nommu UML working with binfmt_elf_fdpic.c.
> I think it is a proper superset of ELF functionality.
>
> Then I would make it a long term goal to see about removing redundancy
> between binfmt_elf.c and binfmt_elf_fdpic.c with a view to merging them
> in the long term.
>
> There is a lot of mostly duplicate code between the two and
> binfmt_elf_fdpic.c does not get half the attention and use binfmt_elf.c
> gets.
thanks for the recommendation. I'll go for this direction.
It would be great if nommu arch (at least) UML can use the regular
binfmt_elf.
-- Hajime
next prev parent reply other threads:[~2024-12-13 22:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 10:12 [PATCH v5 00/13] nommu UML Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 01/13] x86/um: clean up elf specific definitions Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 02/13] x86/um: nommu: elf loader for fdpic Hajime Tazaki
2024-12-12 14:22 ` Eric W. Biederman
2024-12-13 7:19 ` Hajime Tazaki
2024-12-13 20:01 ` Eric W. Biederman
2024-12-13 21:23 ` Hajime Tazaki
2024-12-13 21:53 ` Eric W. Biederman
2024-12-13 22:21 ` Hajime Tazaki [this message]
2024-12-18 5:13 ` Kees Cook
2024-12-12 10:12 ` [PATCH v5 03/13] um: decouple MMU specific code from the common part Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 04/13] um: nommu: memory handling Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 05/13] x86/um: nommu: syscall handling Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 06/13] um: nommu: seccomp syscalls hook Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 07/13] x86/um: nommu: process/thread handling Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 08/13] um: nommu: configure fs register on host syscall invocation Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 09/13] x86/um/vdso: nommu: vdso memory update Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 10/13] x86/um: nommu: signal handling Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 11/13] um: change machine name for uname output Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 12/13] um: nommu: add documentation of nommu UML Hajime Tazaki
2024-12-12 10:12 ` [PATCH v5 13/13] um: nommu: plug nommu code into build system Hajime Tazaki
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=m2o71f5imo.wl-thehajime@gmail.com \
--to=thehajime@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=brauner@kernel.org \
--cc=ebiederm@xmission.com \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-um@lists.infradead.org \
--cc=ricarkol@google.com \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.