From: "Eric W. Biederman" <ebiederm@xmission.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] binfmt: Slightly simplify elf_fdpic_map_file()
Date: Sun, 28 May 2023 11:34:13 -0500 [thread overview]
Message-ID: <87sfbgjtyy.fsf@email.froward.int.ebiederm.org> (raw)
In-Reply-To: <4f5e4096ad7f17716e924b5bd080e5709fc0b84b.1685290790.git.christophe.jaillet@wanadoo.fr> (Christophe JAILLET's message of "Sun, 28 May 2023 18:20:25 +0200")
Christophe JAILLET <christophe.jaillet@wanadoo.fr> writes:
> There is no point in initializing 'load_addr' and 'seg' here, they are both
> re-written just before being used below.
>
> Doing so, 'load_addr' can be moved in the #ifdef CONFIG_MMU section.
>
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
Kees do you maybe want to pick these trivial fixes up?
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> Compile tested on arm, with and without CONFIG_MMU
> ---
> fs/binfmt_elf_fdpic.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/fs/binfmt_elf_fdpic.c b/fs/binfmt_elf_fdpic.c
> index 237ce388d06d..1c6c5832af86 100644
> --- a/fs/binfmt_elf_fdpic.c
> +++ b/fs/binfmt_elf_fdpic.c
> @@ -743,11 +743,12 @@ static int elf_fdpic_map_file(struct elf_fdpic_params *params,
> struct elf32_fdpic_loadmap *loadmap;
> #ifdef CONFIG_MMU
> struct elf32_fdpic_loadseg *mseg;
> + unsigned long load_addr;
> #endif
> struct elf32_fdpic_loadseg *seg;
> struct elf32_phdr *phdr;
> - unsigned long load_addr, stop;
> unsigned nloads, tmp;
> + unsigned long stop;
> int loop, ret;
>
> /* allocate a load map table */
> @@ -768,9 +769,6 @@ static int elf_fdpic_map_file(struct elf_fdpic_params *params,
> loadmap->version = ELF32_FDPIC_LOADMAP_VERSION;
> loadmap->nsegs = nloads;
>
> - load_addr = params->load_addr;
> - seg = loadmap->segs;
> -
> /* map the requested LOADs into the memory space */
> switch (params->flags & ELF_FDPIC_FLAG_ARRANGEMENT) {
> case ELF_FDPIC_FLAG_CONSTDISP:
next prev parent reply other threads:[~2023-05-28 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 16:20 [PATCH 1/2] binfmt: Use struct_size() Christophe JAILLET
2023-05-28 16:20 ` [PATCH 2/2] binfmt: Slightly simplify elf_fdpic_map_file() Christophe JAILLET
2023-05-28 16:34 ` Eric W. Biederman [this message]
2023-05-28 16:32 ` [PATCH 1/2] binfmt: Use struct_size() Eric W. Biederman
2023-05-30 22:52 ` Kees Cook
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=87sfbgjtyy.fsf@email.froward.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=brauner@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=keescook@chromium.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox