From: Richard Henderson <richard.henderson@linaro.org>
To: laurent@vivier.eu, qemu-devel@nongnu.org
Cc: Nicolas Surbayrole <nsurbayrole@quarkslab.com>
Subject: Re: [PATCH] linux-user: Fix executable page of /proc/self/maps
Date: Fri, 5 Mar 2021 10:50:37 -0800 [thread overview]
Message-ID: <fc49596c-56a8-6518-52a7-8d18f26e854c@linaro.org> (raw)
In-Reply-To: <20210305173144.874378-1-nsurbayrole@quarkslab.com>
On 3/5/21 9:31 AM, Nicolas Surbayrole wrote:
> The guest binary and libraries are not always mapped with the
> executable bit in the host process. The guest may read a
> /proc/self/maps with no executable address range. The
> patch bases the perm fields against the guest permission inside
> Qemu.
>
> Signed-off-by: Nicolas Surbayrole <nsurbayrole@quarkslab.com>
> ---
> linux-user/syscall.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 389ec09764..77c40a274f 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -7888,9 +7888,9 @@ static int open_self_maps(void *cpu_env, int fd)
> count = dprintf(fd, TARGET_ABI_FMT_ptr "-" TARGET_ABI_FMT_ptr
> " %c%c%c%c %08" PRIx64 " %s %"PRId64,
> h2g(min), h2g(max - 1) + 1,
> - e->is_read ? 'r' : '-',
> - e->is_write ? 'w' : '-',
> - e->is_exec ? 'x' : '-',
> + (flags & PROT_READ) ? 'r' : '-',
> + (flags & PROT_WRITE) ? 'w' : '-',
> + (flags & PROT_EXEC) ? 'x' : '-',
Use PAGE_*, as those are the bits in flags. These three just happen to be the
same.
While we're at it, use PAGE_WRITE_ORG -- PAGE_WRITE may be removed on a rwx
page in which we've translated code.
r~
> e->is_priv ? 'p' : '-',
> (uint64_t) e->offset, e->dev, e->inode);
> if (path) {
>
prev parent reply other threads:[~2021-03-05 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 17:31 [PATCH] linux-user: Fix executable page of /proc/self/maps Nicolas Surbayrole
2021-03-05 18:50 ` Richard Henderson [this message]
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=fc49596c-56a8-6518-52a7-8d18f26e854c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=laurent@vivier.eu \
--cc=nsurbayrole@quarkslab.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).