From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: patches@linaro.org, Riku Voipio <riku.voipio@iki.fi>,
Chanho Park <parkch98@gmail.com>
Subject: [Qemu-devel] [PATCH for-2.7] linux-user: Fix llseek with high bit of offset_low set
Date: Thu, 11 Aug 2016 18:59:39 +0100 [thread overview]
Message-ID: <1470938379-1133-1-git-send-email-peter.maydell@linaro.org> (raw)
The llseek syscall takes two 32-bit arguments, offset_high
and offset_low, which must be combined to form a single
64-bit offset. Unfortunately we were combining them with
(uint64_t)arg2 << 32) | arg3
and arg3 is a signed type; this meant that when promoting
arg3 to a 64-bit type it would be sign-extended. The effect
was that if the offset happened to have bit 31 set then
this bit would get sign-extended into all of bits 63..32.
Explicitly cast arg3 to abi_ulong to avoid the erroneous
sign extension.
Reported-by: Chanho Park <parkch98@gmail.com>
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
Long-standing bug and we're quite close to 2.7 but the
fix is trivial so if somebody would like to review it
I think we could put it in...
linux-user/syscall.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/syscall.c b/linux-user/syscall.c
index ebdb753..b4e21d3 100644
--- a/linux-user/syscall.c
+++ b/linux-user/syscall.c
@@ -9406,7 +9406,7 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
{
int64_t res;
#if !defined(__NR_llseek)
- res = lseek(arg1, ((uint64_t)arg2 << 32) | arg3, arg5);
+ res = lseek(arg1, ((uint64_t)arg2 << 32) | (abi_ulong)arg3, arg5);
if (res == -1) {
ret = get_errno(res);
} else {
--
2.7.4
next reply other threads:[~2016-08-11 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 17:59 Peter Maydell [this message]
2016-08-15 13:41 ` [Qemu-devel] [PATCH for-2.7] linux-user: Fix llseek with high bit of offset_low set Chanho Park
2016-08-16 13:44 ` Riku Voipio
2016-08-16 16:10 ` Peter Maydell
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=1470938379-1133-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=parkch98@gmail.com \
--cc=patches@linaro.org \
--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).