All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Hajime Tazaki <thehajime@gmail.com>
Cc: linux-um@lists.infradead.org, ricarkol@google.com,
	Liam.Howlett@oracle.com, Eric Biederman <ebiederm@xmission.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <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: Tue, 17 Dec 2024 21:13:29 -0800	[thread overview]
Message-ID: <202412172113.21E002F0@keescook> (raw)
In-Reply-To: <d387e58f08b929357a2651e82d2ee18bcf681e40.1733998168.git.thehajime@gmail.com>

On Thu, Dec 12, 2024 at 07:12:09PM +0900, Hajime Tazaki wrote:
> As UML supports CONFIG_MMU=n case, it has to use an alternate ELF
> loader, FDPIC ELF loader.  In this commit, we added necessary
> definitions in the arch, as UML has not been used so far.  It also
> updates Kconfig file to use BINFMT_ELF_FDPIC under !MMU environment.
> 
> Cc: Eric Biederman <ebiederm@xmission.com>
> Cc: Kees Cook <kees@kernel.org>
> Cc: Alexander Viro <viro@zeniv.linux.org.uk>
> Cc: Christian Brauner <brauner@kernel.org>
> Cc: Jan Kara <jack@suse.cz>
> Cc: linux-mm@kvack.org
> Cc: linux-fsdevel@vger.kernel.org
> Signed-off-by: Hajime Tazaki <thehajime@gmail.com>

Acked-by: Kees Cook <kees@kernel.org>

-- 
Kees Cook


  parent reply	other threads:[~2024-12-18  5:18 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
2024-12-18  5:13   ` Kees Cook [this message]
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=202412172113.21E002F0@keescook \
    --to=kees@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=brauner@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-um@lists.infradead.org \
    --cc=ricarkol@google.com \
    --cc=thehajime@gmail.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.