From: Laurent Vivier <laurent@vivier.eu>
To: Patrick Venture <venture@google.com>
Cc: qemu-devel@nongnu.org, scw@google.com
Subject: Re: [PATCH v2 1/2] linux-user: rt_sigprocmask, check read perms first
Date: Wed, 26 Jan 2022 20:26:35 +0100 [thread overview]
Message-ID: <48f25af9-fc8f-aab3-bf34-f2d1ed013390@vivier.eu> (raw)
In-Reply-To: <20220126175850.1904968-2-venture@google.com>
Le 26/01/2022 à 18:58, Patrick Venture a écrit :
> From: Shu-Chun Weng <scw@google.com>
>
> Linux kernel does it this way (checks read permission before validating `how`)
> and the latest version of ABSL's `AddressIsReadable()` depends on this
> behavior.
>
> c.f. https://github.com/torvalds/linux/blob/9539ba4308ad5bdca6cb41c7b73cbb9f796dcdd7/kernel/signal.c#L3147
> Reviewed-by: Patrick Venture <venture@google.com>
> Signed-off-by: Shu-Chun Weng <scw@google.com>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
but you must resend the patch: you are not the author, but you have to add your Signed-off-by.
(and now you can add my reviewed-by)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/SubmittingPatches?id=f6f94e2ab1b33f0082ac22d71f66385a60d8157f#n296
Thanks,
Laurent
> ---
> linux-user/syscall.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 5950222a77..34bd819e38 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -9508,6 +9508,13 @@ static abi_long do_syscall1(void *cpu_env, int num, abi_long arg1,
> }
>
> if (arg2) {
> + p = lock_user(VERIFY_READ, arg2, sizeof(target_sigset_t), 1);
> + if (!p) {
> + return -TARGET_EFAULT;
> + }
> + target_to_host_sigset(&set, p);
> + unlock_user(p, arg2, 0);
> + set_ptr = &set;
> switch(how) {
> case TARGET_SIG_BLOCK:
> how = SIG_BLOCK;
> @@ -9521,11 +9528,6 @@ static abi_long do_syscall1(void *cpu_env, int num, abi_long arg1,
> default:
> return -TARGET_EINVAL;
> }
> - if (!(p = lock_user(VERIFY_READ, arg2, sizeof(target_sigset_t), 1)))
> - return -TARGET_EFAULT;
> - target_to_host_sigset(&set, p);
> - unlock_user(p, arg2, 0);
> - set_ptr = &set;
> } else {
> how = 0;
> set_ptr = NULL;
next prev parent reply other threads:[~2022-01-26 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 17:58 [PATCH v2 0/2] linux-user: check read permissions before how Patrick Venture
2022-01-26 17:58 ` [PATCH v2 1/2] linux-user: rt_sigprocmask, check read perms first Patrick Venture
2022-01-26 19:26 ` Laurent Vivier [this message]
2022-01-26 21:10 ` Patrick Venture
2022-01-26 17:58 ` [PATCH v2 2/2] linux-user: sigprocmask " Patrick Venture
2022-01-26 19:26 ` Laurent Vivier
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=48f25af9-fc8f-aab3-bf34-f2d1ed013390@vivier.eu \
--to=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=scw@google.com \
--cc=venture@google.com \
/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).