linux-kernel - Re: [PATCH -next] pstore: fix printk format warning in ram.c

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 for Android: free password hash cracker in your pocket

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

Message-ID: <4FE3B6A9.60109@xenotime.net>
Date:	Thu, 21 Jun 2012 17:04:57 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Randy Dunlap <rdunlap@...otime.net>
CC:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Marco Stornelli <marco.stornelli@...il.com>,
	Kees Cook <keescook@...omium.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH -next] pstore: fix printk format warning in ram.c

Greg,
This patch is still needed in linux-next.....


also:
Acked-by: Kees Cook <keescook@...omium.org>



On 06/15/2012 12:19 PM, Randy Dunlap wrote:

> From: Randy Dunlap <rdunlap@...otime.net>
> 
> Fix printk format warning (on i386) in pstore:
> 
> fs/pstore/ram.c:378:3: warning: format '%lu' expects type 'long unsigned int', but argument 2 has type 'size_t'
> 
> Signed-off-by: Randy Dunlap <rdunlap@...otime.net>
> ---
>  fs/pstore/ram.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> --- linux-next-20120615.orig/fs/pstore/ram.c
> +++ linux-next-20120615/fs/pstore/ram.c
> @@ -375,7 +375,7 @@ static int __init ramoops_probe(struct p
>  		goto fail_init_cprz;
>  
>  	if (!cxt->przs && !cxt->cprz) {
> -		pr_err("memory size too small, minimum is %lu\n",
> +		pr_err("memory size too small, minimum is %zu\n",
>  			cxt->console_size + cxt->record_size);
>  		goto fail_cnt;
>  	}
> 



-- 
~Randy
--
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/