linux-kernel - Re: linux 2.6.23-rc7

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: <alpine.DEB.0.999.0709222212050.27608@mtl.rackplans.net>
Date:	Sat, 22 Sep 2007 22:23:59 -0400 (EDT)
From:	Gerhard Mack <gmack@...erfire.net>
To:	WANG Cong <xiyou.wangcong@...il.com>
cc:	Dave Haywood <tla@....selfip.net>, linux-kernel@...r.kernel.org
Subject: Re: linux 2.6.23-rc7 - 14 compile warnings

On Sat, 22 Sep 2007, WANG Cong wrote:

> >Summary:
> >  CC      mm/slub.o
> >mm/slub.c: In function 'kfree':
> >mm/slub.c:2491: warning: passing argument 3 of 'slab_free' discards
> >qualifiers from pointer target type

static void __slab_free(struct kmem_cache *s, struct page *page,
                                        void *x, void *addr)
but ..

void kfree(const void *x)

void is not the same as const void.

> >  CC      fs/autofs4/symlink.o
> >fs/autofs4/symlink.c: In function 'autofs4_follow_link':
> >fs/autofs4/symlink.c:18: warning: passing argument 2 of 'nd_set_link'
> >discards qualifiers from pointer target type

Once again ino->u.symlink is a const char and it's dropping the const.

> 
> These two warnings are suspicious. Explicit casts are already there, how
> they come out? Or gcc bugs?
> 

gcc is perfectly justified when warning about dropping const. 

	Gerhard

--
Gerhard Mack

gmack@...erfire.net

<>< As a computer I find your faith in technology amusing.
-
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/