From: Laurent Vivier <laurent@vivier.eu>
To: Helge Deller <deller@gmx.de>, Riku Voipio <riku.voipio@iki.fi>,
qemu-devel@nongnu.org
Subject: Re: [PATCH] linux-user: Drop unnecessary check in signalfd4 syscall
Date: Sat, 25 Apr 2020 10:39:40 +0200 [thread overview]
Message-ID: <c9f3644e-21c8-600b-4bf6-d55e6c52153f@vivier.eu> (raw)
In-Reply-To: <20200424210422.GB26282@ls3530.fritz.box>
Le 24/04/2020 à 23:04, Helge Deller a écrit :
> The signalfd4() syscall takes optional O_NONBLOCK and O_CLOEXEC fcntl
> flags. If the user gave any other invalid flags, the host syscall will
> return correct error codes, so simply drop the extra check here.
>
> Signed-off-by: Helge Deller <deller@gmx.de>
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 05f03919ff..ebf0d38321 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -7176,9 +7176,6 @@ static abi_long do_signalfd4(int fd, abi_long mask, int flags)
> sigset_t host_mask;
> abi_long ret;
>
> - if (flags & ~(TARGET_O_NONBLOCK | TARGET_O_CLOEXEC)) {
> - return -TARGET_EINVAL;
> - }
> if (!lock_user_struct(VERIFY_READ, target_mask, mask, 1)) {
> return -TARGET_EFAULT;
> }
>
Perhaps we want to trigger the TARGET_EINVAL before the TARGET_EFAULT if
we have both cases?
But I've checked the kernel, and the kernel does a copy_from_user()
before checking the flags, but it returns EINVAL rather than EFAULT.
We can remove the flags checking but we should also change TARGET_EFAULT
by TARGET_EINVAL.
Thanks,
Laurent
next prev parent reply other threads:[~2020-04-25 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 21:04 [PATCH] linux-user: Drop unnecessary check in signalfd4 syscall Helge Deller
2020-04-25 8:39 ` Laurent Vivier [this message]
2020-04-25 9:24 ` Helge Deller
2020-04-25 10:03 ` Laurent Vivier
2020-04-25 21:48 ` Helge Deller
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=c9f3644e-21c8-600b-4bf6-d55e6c52153f@vivier.eu \
--to=laurent@vivier.eu \
--cc=deller@gmx.de \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).