From: Andreas Schwab <schwab@suse.de>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Laurent Vivier <laurent@vivier.eu>, qemu-devel@nongnu.org
Subject: Re: [PATCH] linux-user: fix layout of struct target_msq_id_ds
Date: Thu, 09 Oct 2025 16:12:56 +0200 [thread overview]
Message-ID: <mvmwm54duzb.fsf@suse.de> (raw)
In-Reply-To: <97a43b68-7f68-4f8f-a647-0967b604267d@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Thu, 9 Oct 2025 15:55:07 +0200")
On Okt 09 2025, Philippe Mathieu-Daudé wrote:
> Hi Andreas,
>
> On 9/10/25 14:56, Andreas Schwab wrote:
>> The msg_lspid and msg_lrpid members are of type pid_t, which is a 32-bit
>> integer.
>> Signed-off-by: Andreas Schwab <schwab@suse.de>
>> ---
>> linux-user/syscall.c | 12 ++++++------
>> 1 file changed, 6 insertions(+), 6 deletions(-)
>> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
>> index 0956a7b310..3dcdb3ef42 100644
>> --- a/linux-user/syscall.c
>> +++ b/linux-user/syscall.c
>> @@ -4185,8 +4185,8 @@ struct target_msqid_ds
>> abi_ulong __msg_cbytes;
>> abi_ulong msg_qnum;
>> abi_ulong msg_qbytes;
>> - abi_ulong msg_lspid;
>> - abi_ulong msg_lrpid;
>> + unsigned int msg_lspid;
>> + unsigned int msg_lrpid;
>
> Why not use the explicit 'uint32_t' type?
linux-user/syscall.c often just uses int for 32-bit integers, and it's
the same as x86_64/target_syscall.h:struct target_msgid64_ds.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2025-10-09 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 12:56 [PATCH] linux-user: fix layout of struct target_msq_id_ds Andreas Schwab
2025-10-09 13:55 ` Philippe Mathieu-Daudé
2025-10-09 14:12 ` Andreas Schwab [this message]
2025-10-09 15:42 ` Richard Henderson
2025-10-09 15:46 ` Richard Henderson
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=mvmwm54duzb.fsf@suse.de \
--to=schwab@suse.de \
--cc=laurent@vivier.eu \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).