[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110204220944.GN5503@outflux.net>
Date: Fri, 4 Feb 2011 14:09:44 -0800
From: Kees Cook <kees.cook@...onical.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, Joe Perches <joe@...ches.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Tejun Heo <tj@...nel.org>, Marcus Meissner <meissner@...e.de>,
Jason Wessel <jason.wessel@...driver.com>,
Eugene Teo <eugeneteo@...nel.org>,
Bjorn Helgaas <bjorn.helgaas@...com>,
Len Brown <len.brown@...el.com>,
Changli Gao <xiaosuo@...il.com>,
Dan Rosenberg <drosenberg@...curity.com>
Subject: Re: [PATCH v2] use %pK for /proc/kallsyms and /proc/modules
Hi Andrew,
On Fri, Feb 04, 2011 at 02:03:51PM -0800, Andrew Morton wrote:
> kernel/kallsyms.c: In function 's_show':
> kernel/kallsyms.c:481: warning: format '%p' expects type 'void *', but argument 3 has type 'long unsigned int'
> kernel/kallsyms.c:484: warning: format '%p' expects type 'void *', but argument 3 has type 'long unsigned int'
> kernel/module.c: In function 'module_sect_show':
> kernel/module.c:1171: warning: format '%p' expects type 'void *', but argument 3 has type 'long unsigned int'
> kernel/module.c:1171: warning: format '%p' expects type 'void *', but argument 3 has type 'long unsigned int'
>
> I'm struggling to see how this could have been compile-time or runtime
> tested?
I run-time tested it plenty. The thread contains the various discussions
about compile-time warnings, so I suspect in the last version, I didn't go
examine the warnings (since the origin of the other warnings went away).
I can send a patch to fix it up to cast everything to (void*) if you want?
-Kees
--
Kees Cook
Ubuntu Security Team
--
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/
Powered by blists - more mailing lists