From: Riku Voipio <riku.voipio@iki.fi>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Mike Frysinger <vapier@gentoo.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] linux-user/syscall.c: Enforce pselect6 sigset size restrictions
Date: Tue, 28 Jun 2011 14:51:49 +0300 [thread overview]
Message-ID: <20110628115149.GA17577@afflict.kos.to> (raw)
In-Reply-To: <1309260117-28334-1-git-send-email-peter.maydell@linaro.org>
On Tue, Jun 28, 2011 at 12:21:57PM +0100, Peter Maydell wrote:
> Enforce the same restriction on the size of the sigset passed to
> pselect6 as the Linux kernel does. This is both correct and silences
> a gcc 4.6 warning about a write-only variable.
Odd but true, after all the trouble of passing the size as packed variable,
even the kernel bothers nothing but check that it matches with
sizeof(sigset_t)...
I'll include this and your other two patches for the next round.
Riku
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> This really is the last gcc 4.6 warning fix!
>
> linux-user/syscall.c | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index fed7a8f..feb2501 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -5684,6 +5684,11 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
>
> if (arg_sigset) {
> sig.set = &set;
> + if (arg_sigsize != sizeof(*target_sigset)) {
> + /* Like the kernel, we enforce correct size sigsets */
> + ret = -TARGET_EINVAL;
> + goto fail;
> + }
> target_sigset = lock_user(VERIFY_READ, arg_sigset,
> sizeof(*target_sigset), 1);
> if (!target_sigset) {
> --
> 1.7.5.3
next prev parent reply other threads:[~2011-06-28 11:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 11:21 [Qemu-devel] [PATCH] linux-user/syscall.c: Enforce pselect6 sigset size restrictions Peter Maydell
2011-06-28 11:51 ` Riku Voipio [this message]
2011-06-28 11:54 ` Peter Maydell
2011-06-28 16:14 ` Mike Frysinger
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=20110628115149.GA17577@afflict.kos.to \
--to=riku.voipio@iki.fi \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vapier@gentoo.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).