linux-kernel - Re: [PATCH 3/3] staging/sep: Fix sparse printk format warning

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CF434B6.3030503@gmail.com>
Date:	Tue, 30 Nov 2010 00:18:14 +0100
From:	Jiri Slaby <jirislaby@...il.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	Peter Hüwe <PeterHuewe@....de>,
	devel@...verdev.osuosl.org, Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org, Mark Allyn <mark.a.allyn@...el.com>,
	Joe Perches <joe@...ches.com>,
	Ben Hutchings <ben@...adent.org.uk>,
	Alan Cox <alan@...ux.intel.com>
Subject: Re: [PATCH 3/3] staging/sep: Fix sparse printk format warning

On 11/29/2010 11:01 PM, Randy Dunlap wrote:
> On Mon, 29 Nov 2010 22:59:11 +0100 Peter Hüwe wrote:
> 
>>> Are you sure?  I'm used to these being gcc warnings, not sparse.
>> You're right - these are generated by gcc ;) sorry for the confusion.
>>
>>> Also, this fixes the warnings on x86_64 but not on x86_32/i386:
>> You're right again, I'm on x86_64 - so what should I use instead?
> 
> I dunno, I've tried to fix this myself and the only thing that I have
> been successful with is casting those ioctl values to (unsigned long)
> and using %lx to print them.

What about to remove that completely :)? I don't see what that could be
good for -- everybody from userspace can print it...

regards,
-- 
js
--
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/