From: Christian Brauner <brauner@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the vfs-brauner tree
Date: Mon, 20 Jan 2025 13:15:07 +0100 [thread overview]
Message-ID: <20250120-juror-halme-dc19277bc465@brauner> (raw)
In-Reply-To: <20250120192504.4a1965a0@canb.auug.org.au>
On Mon, Jan 20, 2025 at 07:25:04PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> On Tue, 14 Jan 2025 16:48:12 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Thu, 19 Dec 2024 17:32:35 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > >
> > > On Fri, 13 Dec 2024 15:27:24 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> > > >
> > > > After merging the vfs-brauner tree, today's linux-next build (powerpc
> > > > allyesconfig) produced these warnings:
> > > >
> > > > samples/vfs/test-list-all-mounts.c: In function 'main':
> > > > samples/vfs/test-list-all-mounts.c:175:58: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 3 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> > > > 175 | printf("Listing %u mounts for mount namespace %llu\n",
> > > > | ~~~^
> > > > | |
> > > > | long long unsigned int
> > > > | %lu
> > > > 176 | info.nr_mounts, info.mnt_ns_id);
> > > > | ~~~~~~~~~~~~~~
> > > > | |
> > > > | __u64 {aka long unsigned int}
> > > > samples/vfs/test-list-all-mounts.c:186:83: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 3 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> > > > 186 | printf("Finished listing %u mounts for mount namespace %llu\n\n",
> > > > | ~~~^
> > > > | |
> > > > | long long unsigned int
> > > > | %lu
> > > > 187 | info.nr_mounts, info.mnt_ns_id);
> > > > | ~~~~~~~~~~~~~~
> > > > | |
> > > > | __u64 {aka long unsigned int}
> > > > samples/vfs/test-list-all-mounts.c:199:74: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 3 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> > > > 199 | printf("Listing %u mounts for mount namespace %llu\n",
> > > > | ~~~^
> > > > | |
> > > > | long long unsigned int
> > > > | %lu
> > > > 200 | info.nr_mounts, info.mnt_ns_id);
> > > > | ~~~~~~~~~~~~~~
> > > > | |
> > > > | __u64 {aka long unsigned int}
> > > > samples/vfs/test-list-all-mounts.c:218:64: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> > > > 218 | printf("Failed to statmount(%llu) in mount namespace(%llu)\n",
> > > > | ~~~^
> > > > | |
> > > > | long long unsigned int
> > > > | %lu
> > > > 219 | last_mnt_id, info.mnt_ns_id);
> > > > | ~~~~~~~~~~~
> > > > | |
> > > > | __u64 {aka long unsigned int}
> > > > samples/vfs/test-list-all-mounts.c:218:89: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 3 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> > > > 218 | printf("Failed to statmount(%llu) in mount namespace(%llu)\n",
> > > > | ~~~^
> > > > | |
> > > > | long long unsigned int
> > > > | %lu
> > > > 219 | last_mnt_id, info.mnt_ns_id);
> > > > | ~~~~~~~~~~~~~~
> > > > | |
> > > > | __u64 {aka long unsigned int}
> > > > samples/vfs/test-list-all-mounts.c:223:47: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 2 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> > > > 223 | printf("mnt_id:\t\t%llu\nmnt_parent_id:\t%llu\nfs_type:\t%s\nmnt_root:\t%s\nmnt_point:\t%s\nmnt_opts:\t%s\n\n",
> > > > | ~~~^
> > > > | |
> > > > | long long unsigned int
> > > > | %lu
> > > > 224 | stmnt->mnt_id,
> > > > | ~~~~~~~~~~~~~
> > > > | |
> > > > | __u64 {aka long unsigned int}
> > > > samples/vfs/test-list-all-mounts.c:223:69: warning: format '%llu' expects argument of type 'long long unsigned int', but argument 3 has type '__u64' {aka 'long unsigned int'} [-Wformat=]
> > > > 223 | printf("mnt_id:\t\t%llu\nmnt_parent_id:\t%llu\nfs_type:\t%s\nmnt_root:\t%s\nmnt_point:\t%s\nmnt_opts:\t%s\n\n",
> > > > | ~~~^
> > > > | |
> > > > | long long unsigned int
> > > > | %lu
> > > > 224 | stmnt->mnt_id,
> > > > 225 | stmnt->mnt_parent_id,
> > > > | ~~~~~~~~~~~~~~~~~~~~
> > > > | |
> > > > | __u64 {aka long unsigned int}
> > > >
> > > > Introduced by commit
> > > >
> > > > 7b1da09dc088 ("samples: add test-list-all-mounts")
> > >
> > > I am still seeing these warnings.
> >
> > Still there ...
>
> Ping?
Thanks for the reminder.
This is now fixed.
next prev parent reply other threads:[~2025-01-20 12:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 4:27 linux-next: build warnings after merge of the vfs-brauner tree Stephen Rothwell
2024-12-19 6:32 ` Stephen Rothwell
2025-01-14 5:48 ` Stephen Rothwell
2025-01-20 8:25 ` Stephen Rothwell
2025-01-20 12:15 ` Christian Brauner [this message]
2025-01-20 20:55 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2025-12-16 0:52 Stephen Rothwell
2025-11-17 6:47 Stephen Rothwell
2025-11-12 2:42 Stephen Rothwell
2025-11-12 10:10 ` Mateusz Guzik
2025-11-12 10:55 ` Stephen Rothwell
2025-11-12 10:57 ` Mateusz Guzik
2025-07-17 7:36 Stephen Rothwell
2025-07-22 10:24 ` Jann Horn
2025-03-05 10:07 Stephen Rothwell
2025-03-05 10:55 ` David Disseldorp
2024-12-11 3:37 Stephen Rothwell
2024-12-19 6:31 ` Stephen Rothwell
2024-12-19 12:40 ` Jeff Layton
2024-12-19 20:36 ` Stephen Rothwell
2025-01-06 13:50 ` Geert Uytterhoeven
2024-10-09 6:29 Stephen Rothwell
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=20250120-juror-halme-dc19277bc465@brauner \
--to=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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