From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
"Eric W . Biederman" <ebiederm@xmission.com>,
linux-fsdevel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Jeremy Kerr <jk@ozlabs.org>
Subject: Re: [PATCH 8/8] exec: open code copy_string_kernel
Date: Sat, 18 Apr 2020 10:15:42 +0200 [thread overview]
Message-ID: <ffea91ee-f386-9d19-0bc9-ab59eb7b9a41@c-s.fr> (raw)
In-Reply-To: <20200414070142.288696-9-hch@lst.de>
Le 14/04/2020 à 09:01, Christoph Hellwig a écrit :
> Currently copy_string_kernel is just a wrapper around copy_strings that
> simplifies the calling conventions and uses set_fs to allow passing a
> kernel pointer. But due to the fact the we only need to handle a single
> kernel argument pointer, the logic can be sigificantly simplified while
> getting rid of the set_fs.
Instead of duplicating almost identical code, can you write a function
that takes whether the source is from user or from kernel, then you just
do things like:
if (from_user)
len = strnlen_user(str, MAX_ARG_STRLEN);
else
len = strnlen(str, MAX_ARG_STRLEN);
if (from_user)
copy_from_user(kaddr+offset, str, bytes_to_copy);
else
memcpy(kaddr+offset, str, bytes_to_copy);
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/exec.c | 43 ++++++++++++++++++++++++++++++++++---------
> 1 file changed, 34 insertions(+), 9 deletions(-)
>
> diff --git a/fs/exec.c b/fs/exec.c
> index b2a77d5acede..ea90af1fb236 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -592,17 +592,42 @@ static int copy_strings(int argc, struct user_arg_ptr argv,
> */
> int copy_string_kernel(const char *arg, struct linux_binprm *bprm)
> {
> - int r;
> - mm_segment_t oldfs = get_fs();
> - struct user_arg_ptr argv = {
> - .ptr.native = (const char __user *const __user *)&arg,
> - };
> + int len = strnlen(arg, MAX_ARG_STRLEN) + 1 /* terminating NUL */;
> + unsigned long pos = bprm->p;
> +
> + if (len == 0)
> + return -EFAULT;
> + if (!valid_arg_len(bprm, len))
> + return -E2BIG;
> +
> + /* We're going to work our way backwards. */
> + arg += len;
> + bprm->p -= len;
> + if (IS_ENABLED(CONFIG_MMU) && bprm->p < bprm->argmin)
> + return -E2BIG;
> +
> + while (len > 0) {
> + unsigned int bytes_to_copy = min_t(unsigned int, len,
> + min_not_zero(offset_in_page(pos), PAGE_SIZE));
> + struct page *page;
> + char *kaddr;
>
> - set_fs(KERNEL_DS);
> - r = copy_strings(1, argv, bprm);
> - set_fs(oldfs);
> + pos -= bytes_to_copy;
> + arg -= bytes_to_copy;
> + len -= bytes_to_copy;
>
> - return r;
> + page = get_arg_page(bprm, pos, 1);
> + if (!page)
> + return -E2BIG;
> + kaddr = kmap_atomic(page);
> + flush_arg_page(bprm, pos & PAGE_MASK, page);
> + memcpy(kaddr + offset_in_page(pos), arg, bytes_to_copy);
> + flush_kernel_dcache_page(page);
> + kunmap_atomic(kaddr);
> + put_arg_page(page);
> + }
> +
> + return 0;
> }
> EXPORT_SYMBOL(copy_string_kernel);
>
>
Christophe
next prev parent reply other threads:[~2020-04-18 8:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 7:01 remove set_fs calls from the exec and coredump code v2 Christoph Hellwig
2020-04-14 7:01 ` [PATCH 1/8] powerpc/spufs: simplify spufs core dumping Christoph Hellwig
2020-04-14 7:01 ` [PATCH 2/8] signal: clean up __copy_siginfo_to_user32 Christoph Hellwig
2020-04-17 21:08 ` Eric W. Biederman
2020-04-17 21:09 ` [PATCH 1/2] signal: Factor copy_siginfo_to_external32 from copy_siginfo_to_user32 Eric W. Biederman
2020-04-18 8:05 ` Christophe Leroy
2020-04-18 11:55 ` Eric W. Biederman
2020-04-19 8:13 ` Christoph Hellwig
2020-04-19 9:46 ` Christophe Leroy
2020-04-19 9:54 ` Christophe Leroy
2020-04-19 8:05 ` Christoph Hellwig
2020-04-17 21:09 ` [PATCH 2/2] signal: Remove the set_fs in binfmt_elf.c:fill_siginfo_note Eric W. Biederman
2020-04-19 8:03 ` [PATCH 2/8] signal: clean up __copy_siginfo_to_user32 Christoph Hellwig
2020-04-14 7:01 ` [PATCH 3/8] signal: replace __copy_siginfo_to_user32 with to_compat_siginfo Christoph Hellwig
2020-04-14 14:00 ` Arnd Bergmann
2020-04-14 7:01 ` [PATCH 4/8] binfmt_elf: open code copy_siginfo_to_user to kernelspace buffer Christoph Hellwig
2020-04-14 13:15 ` Arnd Bergmann
2020-04-15 7:45 ` Christoph Hellwig
2020-04-15 8:20 ` Arnd Bergmann
2020-04-17 13:27 ` Christoph Hellwig
2020-04-17 18:10 ` Eric W. Biederman
2020-04-17 20:06 ` Arnd Bergmann
2020-04-15 3:01 ` Michael Ellerman
2020-04-15 6:19 ` Christoph Hellwig
2020-04-14 7:01 ` [PATCH 5/8] binfmt_elf: remove the set_fs(KERNEL_DS) in elf_core_dump Christoph Hellwig
2020-04-14 7:01 ` [PATCH 6/8] binfmt_elf_fdpic: remove the set_fs(KERNEL_DS) in elf_fdpic_core_dump Christoph Hellwig
2020-04-14 7:01 ` [PATCH 7/8] exec: simplify the copy_strings_kernel calling convention Christoph Hellwig
2020-04-14 7:01 ` [PATCH 8/8] exec: open code copy_string_kernel Christoph Hellwig
2020-04-18 8:15 ` Christophe Leroy [this message]
2020-04-19 8:06 ` Christoph Hellwig
2020-04-19 9:44 ` Christophe Leroy
2020-04-17 22:41 ` remove set_fs calls from the exec and coredump code v2 Eric W. Biederman
2020-04-19 8:19 ` Christoph Hellwig
2020-04-19 11:50 ` Eric W. Biederman
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=ffea91ee-f386-9d19-0bc9-ab59eb7b9a41@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=ebiederm@xmission.com \
--cc=hch@lst.de \
--cc=jk@ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).