From: Qu Wenruo <wqu@suse.com>
To: "Darrick J. Wong" <djwong@kernel.org>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Anand Jain <anand.jain@oracle.com>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] fstests: fix blksize_t printf format warnings across architectures
Date: Thu, 21 Nov 2024 09:40:13 +1030 [thread overview]
Message-ID: <cf150514-d820-4f79-8e19-b479bc93855b@suse.com> (raw)
In-Reply-To: <20241120222152.GD9438@frogsfrogsfrogs>
在 2024/11/21 08:51, Darrick J. Wong 写道:
> On Thu, Nov 21, 2024 at 08:36:58AM +1030, Qu Wenruo wrote:
>>
>>
>> 在 2024/11/20 22:10, Anand Jain 写道:
>>> Fix format string warnings when printing blksize_t values that vary
>>> across architectures. The warning occurs because blksize_t is defined
>>> differently between architectures: aarch64 architectures blksize_t is
>>> int, on x86-64 it's long-int. Cast the values to long. Fixes warnings
>>> as below.
>>>
>>> seek_sanity_test.c:110:45: warning: format '%ld' expects argument of type
>>> 'long int', but argument 3 has type 'blksize_t' {aka 'int'}
>>>
>>> attr_replace_test.c:70:22: warning: format '%ld' expects argument of type
>>> 'long int', but argument 3 has type '__blksize_t' {aka 'int'}
>>
>> Why not just use %zu instead?
>
> From printf(3):
>
> z A following integer conversion corresponds to a size_t
> or ssize_t argument, or a following n conversion corre‐
> sponds to a pointer to a size_t argument.
>
> blksize_t is not a ssize_t.
You're right, it's indeed different and it's more complex than I thought.
blksize_t is __SYSCALL_SLONG_TYPE, which has extra handling on x86_64
with its x32 mode handling.
Only for x86_64 x32 mode it is __SQUAD_TYPE (depending on wordsize
again) otherwise it's __SLONGWORD_TYPE (fixed to long int).
Meanwhile ssize_t is __SWORD_TYPE, which is only dependent on word size.
For 32bit word size it's __int64_t, and for 64bit it's long int.
So blksize_t is more weird than ssize_t.
Then force converting to long (int) is fine.
>
> --D
>
>> Thanks,
>> Qu
>>
>>>
>>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>>> ---
>>> src/attr_replace_test.c | 2 +-
>>> src/seek_sanity_test.c | 2 +-
>>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/src/attr_replace_test.c b/src/attr_replace_test.c
>>> index 1218e7264c8f..5d560a633361 100644
>>> --- a/src/attr_replace_test.c
>>> +++ b/src/attr_replace_test.c
>>> @@ -67,7 +67,7 @@ int main(int argc, char *argv[])
>>> if (ret < 0) die();
>>> size = sbuf.st_blksize * 3 / 4;
>>> if (!size)
>>> - fail("Invalid st_blksize(%ld)\n", sbuf.st_blksize);
>>> + fail("Invalid st_blksize(%ld)\n", (long)sbuf.st_blksize);
Although for this case, I'd prefer to use "long int" just for the sake
of consistency.
Otherwise looks good to me.
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
>>> size = MIN(size, maxsize);
>>> value = malloc(size);
>>> if (!value)
>>> diff --git a/src/seek_sanity_test.c b/src/seek_sanity_test.c
>>> index a61ed3da9a8f..c5930357911f 100644
>>> --- a/src/seek_sanity_test.c
>>> +++ b/src/seek_sanity_test.c
>>> @@ -107,7 +107,7 @@ static int get_io_sizes(int fd)
>>> offset += pos ? 0 : 1;
>>> alloc_size = offset;
>>> done:
>>> - fprintf(stdout, "Allocation size: %ld\n", alloc_size);
>>> + fprintf(stdout, "Allocation size: %ld\n", (long)alloc_size);
>>> return 0;
>>>
>>> fail:
>>
>>
>
next prev parent reply other threads:[~2024-11-20 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-20 11:40 [PATCH] fstests: fix blksize_t printf format warnings across architectures Anand Jain
2024-11-20 16:28 ` Darrick J. Wong
2024-11-21 2:04 ` Anand Jain
2024-11-20 22:06 ` Qu Wenruo
2024-11-20 22:21 ` Darrick J. Wong
2024-11-20 23:10 ` Qu Wenruo [this message]
2025-01-09 15:09 ` [GIT PULL] fstests: btrfs changes staged-20250109 Anand Jain
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=cf150514-d820-4f79-8e19-b479bc93855b@suse.com \
--to=wqu@suse.com \
--cc=anand.jain@oracle.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.