From: Laurent Vivier <laurent@vivier.eu>
To: "Thomas Weißschuh" <thomas@t-8ch.de>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 1/2] linux-user: Add new flag VERIFY_NONE
Date: Mon, 1 May 2023 17:54:44 +0200 [thread overview]
Message-ID: <aac07e1b-5b6d-1c07-cb4b-d5357ca785e8@vivier.eu> (raw)
In-Reply-To: <20230422100314.1650-2-thomas@t-8ch.de>
Le 22/04/2023 à 12:03, Thomas Weißschuh a écrit :
> This can be used to validate that an address range is mapped but without
> being readable or writable.
>
> It will be used by an updated implementation of mincore().
>
> Signed-off-by: Thomas Weißschuh <thomas@t-8ch.de>
> ---
> linux-user/qemu.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/linux-user/qemu.h b/linux-user/qemu.h
> index e2e93fbd1d5d..92f9f5af41c7 100644
> --- a/linux-user/qemu.h
> +++ b/linux-user/qemu.h
> @@ -168,6 +168,7 @@ abi_long do_brk(abi_ulong new_brk);
>
> /* user access */
>
> +#define VERIFY_NONE 0
> #define VERIFY_READ PAGE_READ
> #define VERIFY_WRITE (PAGE_READ | PAGE_WRITE)
>
Applied to my linux-user-for-8.1 branch.
Thanks,
Laurent
next prev parent reply other threads:[~2023-05-01 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 10:03 [PATCH v2 0/2] linux-user: Fix mincore() with PROT_NONE Thomas Weißschuh
2023-04-22 10:03 ` [PATCH v2 1/2] linux-user: Add new flag VERIFY_NONE Thomas Weißschuh
2023-05-01 15:48 ` Laurent Vivier
2023-05-01 15:54 ` Laurent Vivier [this message]
2023-04-22 10:03 ` [PATCH v2 2/2] linux-user: Don't require PROT_READ for mincore Thomas Weißschuh
2023-05-01 15:48 ` Laurent Vivier
2023-05-01 15:54 ` Laurent Vivier
2023-04-23 17:24 ` [PATCH v2 0/2] linux-user: Fix mincore() with PROT_NONE Philippe Mathieu-Daudé
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=aac07e1b-5b6d-1c07-cb4b-d5357ca785e8@vivier.eu \
--to=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=thomas@t-8ch.de \
/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).