Re: linux-next: build warnings after merge of the vfs-brauner tree

From: Stephen Rothwell
Date: Thu Dec 19 2024 - 01:34:22 EST


Hi all,

On Wed, 11 Dec 2024 14:37:01 +1100 Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> wrote:
>
> After merging the vfs-brauner tree, today's linux-next build (powerpc
> allyesconfig) produced these warnings:
>
> samples/vfs/mountinfo.c: In function 'show_propagation':
> samples/vfs/mountinfo.c:104:36: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> 104 | printf(" shared:%llu", sm->mnt_peer_group);
> | ~~~^ ~~~~~~~~~~~~~~~~~~
> | | |
> | | __u64 {aka long unsigned int}
> | long long unsigned int
> | %lu
> samples/vfs/mountinfo.c:106:36: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> 106 | printf(" master:%llu", sm->mnt_master);
> | ~~~^ ~~~~~~~~~~~~~~
> | | |
> | | __u64 {aka long unsigned int}
> | long long unsigned int
> | %lu
> samples/vfs/mountinfo.c:108:52: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> 108 | printf(" propagate_from:%llu", sm->propagate_from);
> | ~~~^ ~~~~~~~~~~~~~~~~~~
> | | |
> | | __u64 {aka long unsigned int}
> | long long unsigned int
> | %lu
> samples/vfs/mountinfo.c: In function 'dump_mountinfo':
> samples/vfs/mountinfo.c:144:42: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 4 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> 144 | printf("0x%lx 0x%lx 0x%llx ", mnt_ns_id, mnt_id, buf->mnt_parent_id);
> | ~~~^ ~~~~~~~~~~~~~~~~~~
> | | |
> | long long unsigned int __u64 {aka long unsigned int}
> | %lx
>
> Introduced by commits
>
> 0c8f746452aa ("samples: add a mountinfo program to demonstrate statmount()/listmount()")
> ee8c840a4a35 ("samples: fix missing nodiratime option and handle propagate_from correctly")
>
> I am not sure why these warnings only turned up today.

I am still seeing these warnings.
--
Cheers,
Stephen Rothwell

Attachment: pgp3QL1QoIyG5.pgp
Description: OpenPGP digital signature