qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Thomas Weißschuh" <thomas@t-8ch.de>, qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH v2 0/2] linux-user: Fix mincore() with PROT_NONE
Date: Sun, 23 Apr 2023 19:24:13 +0200	[thread overview]
Message-ID: <62ef3866-3097-8b13-e7d5-440d72ec645d@linaro.org> (raw)
In-Reply-To: <20230422100314.1650-1-thomas@t-8ch.de>

On 22/4/23 12:03, Thomas Weißschuh wrote:
> The kernel does not require PROT_READ for addresses passed to mincore.
> 
> v1: https://lore.kernel.org/qemu-devel/20230416195103.607948-1-thomas@t-8ch.de/
> v1 -> v2:
> * Introduce symbolic flag VERIFY_NONE instead of hardcoding "0"
> 
> Thomas Weißschuh (2):
>    linux-user: Add new flag VERIFY_NONE
>    linux-user: Don't require PROT_READ for mincore
> 
>   linux-user/qemu.h    | 1 +
>   linux-user/syscall.c | 2 +-
>   2 files changed, 2 insertions(+), 1 deletion(-)

Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>



      parent reply	other threads:[~2023-04-23 17:25 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
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 ` Philippe Mathieu-Daudé [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=62ef3866-3097-8b13-e7d5-440d72ec645d@linaro.org \
    --to=philmd@linaro.org \
    --cc=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).