From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5, part3 01/15] mm: fix build warnings caused by free_reserved_area()
Date: Wed, 8 May 2013 19:45:55 +0100 [thread overview]
Message-ID: <20130508184555.GR18614@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1368026235-5976-2-git-send-email-jiang.liu@huawei.com>
On Wed, May 08, 2013 at 11:17:00PM +0800, Jiang Liu wrote:
> Fix following build warnings cuased by free_reserved_area():
>
> arch/arm/mm/init.c: In function 'mem_init':
> arch/arm/mm/init.c:603:2: warning: passing argument 1 of 'free_reserved_area' makes integer from pointer without a cast [enabled by default]
> free_reserved_area(__va(PHYS_PFN_OFFSET), swapper_pg_dir, 0, NULL);
> ^
> In file included from include/linux/mman.h:4:0,
> from arch/arm/mm/init.c:15:
> include/linux/mm.h:1301:22: note: expected 'long unsigned int' but argument is of type 'void *'
> extern unsigned long free_reserved_area(unsigned long start, unsigned long end,
>
> mm/page_alloc.c: In function 'free_reserved_area':
> >> mm/page_alloc.c:5134:3: warning: passing argument 1 of 'virt_to_phys' makes pointer from integer without a cast [enabled by default]
> In file included from arch/mips/include/asm/page.h:49:0,
> from include/linux/mmzone.h:20,
> from include/linux/gfp.h:4,
> from include/linux/mm.h:8,
> from mm/page_alloc.c:18:
> arch/mips/include/asm/io.h:119:29: note: expected 'const volatile void *' but argument is of type 'long unsigned int'
> mm/page_alloc.c: In function 'free_area_init_nodes':
> mm/page_alloc.c:5030:34: warning: array subscript is below array bounds [-Warray-bounds]
>
> Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Cc: linux-arm-kernel at lists.infradead.org
> Cc: linux-kernel at vger.kernel.org
> Cc: linux-mm at kvack.org
> ---
> arch/arm/mm/init.c | 6 ++++--
> mm/page_alloc.c | 2 +-
> 2 files changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/mm/init.c b/arch/arm/mm/init.c
> index 9a5cdc0..7a82fcd 100644
> --- a/arch/arm/mm/init.c
> +++ b/arch/arm/mm/init.c
> @@ -600,7 +600,8 @@ void __init mem_init(void)
>
> #ifdef CONFIG_SA1111
> /* now that our DMA memory is actually so designated, we can free it */
> - free_reserved_area(__va(PHYS_PFN_OFFSET), swapper_pg_dir, 0, NULL);
> + free_reserved_area((unsigned long)__va(PHYS_PFN_OFFSET),
> + (unsigned long)swapper_pg_dir, 0, NULL);
*YUCK*.
As I've said before, fixing the arguments on free_reserved_area() would
be much better than throwing these horrid casts all over the code.
You're casting pointers to integers, and then immediately casting them
back to pointers in free_reserved_area(). Please fix the function
argument types to be sane.
next prev parent reply other threads:[~2013-05-08 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1368026235-5976-1-git-send-email-jiang.liu@huawei.com>
2013-05-08 15:17 ` [PATCH v5, part3 01/15] mm: fix build warnings caused by free_reserved_area() Jiang Liu
2013-05-08 18:45 ` Russell King - ARM Linux [this message]
2013-05-09 15:42 ` [PATCH] mm: change signature of free_reserved_area() to fix building warnings Jiang Liu
2013-05-08 15:17 ` [PATCH v5, part3 03/15] mm/ARM64: kill poison_init_mem() Jiang Liu
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=20130508184555.GR18614@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).