From: Franklin Snaipe Mathieu <snaipe@diacritic.io>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, snaipe@arista.com,
"Franklin \"Snaipe\" Mathieu" <snaipe@diacritic.io>,
Riku Voipio <riku.voipio@linaro.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: [Qemu-devel] [PATCH] syscall: fixed mincore(2) not failing with ENOMEM
Date: Thu, 16 Feb 2017 08:58:57 +0000 [thread overview]
Message-ID: <20170216085857.23501-1-snaipe@diacritic.io> (raw)
From: "Franklin \"Snaipe\" Mathieu" <snaipe@diacritic.io>
The current implementation of the mincore(2) syscall sets errno to
EFAULT when the region identified by the first two parameters is
invalid.
This goes against the man page specification, where mincore(2) should
only fail with EFAULT when the third parameter is an invalid address;
and fail with ENOMEM when the checked region does not point to mapped
memory.
Signed-off-by: Franklin "Snaipe" Mathieu <snaipe@diacritic.io>
Cc: Riku Voipio <riku.voipio@linaro.org>
Cc: Aurelien Jarno <aurelien@aurel32.net>
---
linux-user/syscall.c | 11 ++++++++---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index 9be8e9530e..af0dd40631 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -11061,11 +11061,16 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
case TARGET_NR_mincore:
{
void *a;
+ ret = -TARGET_ENOMEM;
+ a = lock_user(VERIFY_READ, arg1, arg2, 0);
+ if (!a) {
+ goto fail;
+ }
ret = -TARGET_EFAULT;
- if (!(a = lock_user(VERIFY_READ, arg1,arg2, 0)))
- goto efault;
- if (!(p = lock_user_string(arg3)))
+ p = lock_user_string(arg3)
+ if (!p) {
goto mincore_fail;
+ }
ret = get_errno(mincore(a, arg2, p));
unlock_user(p, arg3, ret);
mincore_fail:
--
2.11.0
next reply other threads:[~2017-02-16 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 8:58 Franklin Snaipe Mathieu [this message]
2017-02-17 0:50 ` [Qemu-devel] [PATCH] syscall: fixed mincore(2) not failing with ENOMEM Fam Zheng
2017-02-17 8:05 ` Franklin "Snaipe" Mathieu
2017-02-17 8:57 ` Franklin Snaipe Mathieu
2017-02-17 8:58 ` [Qemu-devel] [PATCH v2] " Franklin Snaipe Mathieu
2017-02-26 13:12 ` Laurent Vivier
2017-02-17 9:00 ` [Qemu-devel] [PATCH] " Franklin "Snaipe" Mathieu
2017-02-17 10:17 ` Fam Zheng
2017-02-28 6:08 ` Michael Tokarev
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=20170216085857.23501-1-snaipe@diacritic.io \
--to=snaipe@diacritic.io \
--cc=aurelien@aurel32.net \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=riku.voipio@linaro.org \
--cc=snaipe@arista.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).