linux-kernel - Re: [PATCH] ceph: Use %zu to format size_t in ceph_fill_inline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 21 Dec 2014 14:10:19 +0300
From:	Ilya Dryomov <ilya.dryomov@...tank.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Sage Weil <sage@...tank.com>,
	Ceph Development <ceph-devel@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ceph: Use %zu to format size_t in ceph_fill_inline_data()

On Sun, Dec 21, 2014 at 1:56 PM, Geert Uytterhoeven
<geert@...ux-m68k.org> wrote:
> On 32-bit, where size_t is unsigned int:
>
> fs/ceph/addr.c: In function ‘ceph_fill_inline_data’:
> fs/ceph/addr.c:1419: warning: format ‘%lu’ expects type ‘long unsigned int’, but argument 10 has type ‘size_t’
>
> Signed-off-by: Geert Uytterhoeven <geert@...ux-m68k.org>
> ---
>  fs/ceph/addr.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
> index f5013d92a7e6b73d..c81c0e004588b9e2 100644
> --- a/fs/ceph/addr.c
> +++ b/fs/ceph/addr.c
> @@ -1416,7 +1416,7 @@ void ceph_fill_inline_data(struct inode *inode, struct page *locked_page,
>                 }
>         }
>
> -       dout("fill_inline_data %p %llx.%llx len %lu locked_page %p\n",
> +       dout("fill_inline_data %p %llx.%llx len %zu locked_page %p\n",
>              inode, ceph_vinop(inode), len, locked_page);

Sorry, it's been reported by kbuild robot a couple days ago and is
already fixed along with another warning.

Thanks,

                Ilya
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/