From: Johannes Berg <johannes@sipsolutions.net>
To: Benjamin Berg <benjamin@sipsolutions.net>, linux-um@lists.infradead.org
Cc: Benjamin Berg <benjamin.berg@intel.com>
Subject: Re: [PATCH v7 2/7] um: use execveat to create userspace MMs
Date: Thu, 04 Jul 2024 18:49:29 +0200 [thread overview]
Message-ID: <08f0a23907e7c0736ee97d3e2d58fc605e7ca689.camel@sipsolutions.net> (raw)
In-Reply-To: <20240704162717.1417338-3-benjamin@sipsolutions.net>
On Thu, 2024-07-04 at 18:27 +0200, Benjamin Berg wrote:
>
> + /* set a nice name */
> + stub_syscall2(__NR_prctl, PR_SET_NAME, (unsigned long)"uml-userspace");
Is that even needed when you're passing it as argv[0] in execve()? But
whatever, it's fine, just wondering.
> + /* setup signal stack inside stub data */
> + stack.ss_flags = 0;
> + stack.ss_size = STUB_DATA_PAGES * UM_KERN_PAGE_SIZE;
> + stack.ss_sp = (void *)init_data.stub_start + UM_KERN_PAGE_SIZE;
> + stub_syscall2(__NR_sigaltstack, (unsigned long)&stack, 0);
> +
> + /* register SIGSEGV handler (SA_RESTORER, the handler never returns) */
> + sa.sa_flags = SA_ONSTACK | SA_NODEFER | SA_SIGINFO | 0x04000000;
> + sa.sa_handler_ = (void *) init_data.segv_handler;
> + sa.sa_restorer = NULL;
> + sa.sa_mask = 0L; /* No need to mask anything */
most of that init could be in the initializer, except the dynamic ones
of course; the NULL/0 is also unnecessary I guess (though might want the
sa_mask for the comment)
> + struct stub_init_data init_data = {
> + .stub_start = STUB_START,
> + .segv_handler = STUB_CODE +
> + (unsigned long) stub_segv_handler -
> + (unsigned long) __syscall_stub_start,
> + };
> + struct iomem_region *iomem;
> + int ret;
> +
> + init_data.stub_code_fd = phys_mapping(uml_to_phys(__syscall_stub_start),
> + &offset);
> + init_data.stub_code_offset = MMAP_OFFSET(offset);
> +
> + init_data.stub_data_fd = phys_mapping(uml_to_phys(stack), &offset);
> + init_data.stub_data_offset = MMAP_OFFSET(offset);
also could move more here into the initializer
> +static int __init init_stub_exe_fd(void)
> +{
> + size_t len = 0;
maybe that should be called 'written'?
> + int res;
and I technically that should be ssize_t for the write() return value,
not that it'll be big enough to matter
> + while (len < stub_exe_end - stub_exe_start) {
> + res = write(stub_exe_fd, stub_exe_start + len,
> + stub_exe_end - stub_exe_start - len);
> + if (res < 0) {
> + if (errno == EINTR)
> + continue;
> +
> + if (tmpfile)
> + unlink(tmpfile);
> + panic("%s: Failed write to memfd: %d", __func__, errno);
nit: not always memfd now
> + if (!tmpfile) {
> + fcntl(stub_exe_fd, F_ADD_SEALS,
> + F_SEAL_WRITE | F_SEAL_SHRINK | F_SEAL_GROW | F_SEAL_SEAL);
> + } else {
> + /* Only executable by us */
> + if (fchmod(stub_exe_fd, 00500) < 0) {
now it's also readable, so comment doesn't seem right? maybe just remove
it?
> + unlink(tmpfile);
> + panic("Could not make stub binary excutable: %d",
> + errno);
perhaps print -errno?
> + }
> +
> + close(stub_exe_fd);
> + stub_exe_fd = open(tmpfile, O_RDONLY | O_CLOEXEC | O_NOFOLLOW);
> + if (stub_exe_fd < 0) {
> + unlink(tmpfile);
> + panic("Could not reopen stub binary: %d", errno);
same here
johannes
next prev parent reply other threads:[~2024-07-04 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 16:27 [PATCH v7 0/7] Increased address space for 64 bit Benjamin Berg
2024-07-04 16:27 ` [PATCH v7 1/7] um: Add generic stub_syscall1 function Benjamin Berg
2024-07-04 16:27 ` [PATCH v7 2/7] um: use execveat to create userspace MMs Benjamin Berg
2024-07-04 16:49 ` Johannes Berg [this message]
2024-07-04 17:39 ` Benjamin Berg
2024-07-04 16:27 ` [PATCH v7 3/7] um: Fix stub_start address calculation Benjamin Berg
2024-07-04 16:27 ` [PATCH v7 4/7] um: Limit TASK_SIZE to the addressable range Benjamin Berg
2024-07-04 16:27 ` [PATCH v7 5/7] um: Discover host_task_size from envp Benjamin Berg
2024-07-04 16:27 ` [PATCH v7 6/7] um: clear all memory in new userspace processes Benjamin Berg
2024-07-04 16:50 ` Johannes Berg
2024-07-04 16:27 ` [PATCH v7 7/7] um: Add 4 level page table support Benjamin Berg
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=08f0a23907e7c0736ee97d3e2d58fc605e7ca689.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=benjamin.berg@intel.com \
--cc=benjamin@sipsolutions.net \
--cc=linux-um@lists.infradead.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