From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Ilya Leoshkevich" <iii@linux.ibm.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Laurent Vivier" <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH 1/2] linux-user: Fix unaligned memory access in prlimit64 syscall
Date: Thu, 23 Feb 2023 23:17:36 +0100 [thread overview]
Message-ID: <77733ac2-9d30-8262-f6d4-5b1a169f8003@linaro.org> (raw)
In-Reply-To: <20230223215834.166055-2-iii@linux.ibm.com>
On 23/2/23 22:58, Ilya Leoshkevich wrote:
> 32-bit guests may enforce only 4-byte alignment for target_rlimit64,
> whereas 64-bit hosts normally require the 8-byte one. Therefore
> accessing this struct directly is UB.
>
> Fix by adding a local copy.
Shouldn't we fix that globally in __get_user/__put_user?
> Fixes: 163a05a8398b ("linux-user: Implement prlimit64 syscall")
> Reported-by: Richard Henderson <richard.henderson@linaro.org>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> ---
> 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 a6c426d73cf..8ae7696d8f1 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -12876,7 +12876,7 @@ static abi_long do_syscall1(CPUArchState *cpu_env, int num, abi_long arg1,
> case TARGET_NR_prlimit64:
> {
> /* args: pid, resource number, ptr to new rlimit, ptr to old rlimit */
> - struct target_rlimit64 *target_rnew, *target_rold;
> + struct target_rlimit64 *target_rnew, *target_rold, tmp;
> struct host_rlimit64 rnew, rold, *rnewp = 0;
> int resource = target_to_host_resource(arg2);
>
> @@ -12886,8 +12886,9 @@ static abi_long do_syscall1(CPUArchState *cpu_env, int num, abi_long arg1,
> if (!lock_user_struct(VERIFY_READ, target_rnew, arg3, 1)) {
> return -TARGET_EFAULT;
> }
> - rnew.rlim_cur = tswap64(target_rnew->rlim_cur);
> - rnew.rlim_max = tswap64(target_rnew->rlim_max);
> + memcpy(&tmp, target_rnew, sizeof(tmp));
> + rnew.rlim_cur = tswap64(tmp.rlim_cur);
> + rnew.rlim_max = tswap64(tmp.rlim_max);
> unlock_user_struct(target_rnew, arg3, 0);
> rnewp = &rnew;
> }
> @@ -12897,8 +12898,9 @@ static abi_long do_syscall1(CPUArchState *cpu_env, int num, abi_long arg1,
> if (!lock_user_struct(VERIFY_WRITE, target_rold, arg4, 1)) {
> return -TARGET_EFAULT;
> }
> - target_rold->rlim_cur = tswap64(rold.rlim_cur);
> - target_rold->rlim_max = tswap64(rold.rlim_max);
> + tmp.rlim_cur = tswap64(rold.rlim_cur);
> + tmp.rlim_max = tswap64(rold.rlim_max);
> + memcpy(target_rold, &tmp, sizeof(*target_rold));
> unlock_user_struct(target_rold, arg4, 1);
> }
> return ret;
next prev parent reply other threads:[~2023-02-23 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 21:58 [PATCH 0/2] linux-user: Fix unaligned memory access in prlimit64 syscall Ilya Leoshkevich
2023-02-23 21:58 ` [PATCH 1/2] " Ilya Leoshkevich
2023-02-23 22:17 ` Philippe Mathieu-Daudé [this message]
2023-02-23 22:24 ` Ilya Leoshkevich
2023-02-23 22:31 ` Richard Henderson
2023-02-23 22:45 ` Ilya Leoshkevich
2023-02-23 21:58 ` [PATCH 2/2] tests/tcg/linux-test: Add linux-fork-trap test Ilya Leoshkevich
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=77733ac2-9d30-8262-f6d4-5b1a169f8003@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=borntraeger@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).