linux-kernel - Re: linux-next: Tree for April 30 (CONFIG

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]

Date:	Wed, 05 May 2010 14:35:03 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Greg KH <gregkh@...e.de>
Cc:	Randy Dunlap <randy.dunlap@...cle.com>, linux-next@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: linux-next: Tree for April 30 (CONFIG_SYSFS=n)

Greg KH <gregkh@...e.de> writes:

> On Wed, May 05, 2010 at 09:17:38AM -0700, Randy Dunlap wrote:
>> On Fri, 30 Apr 2010 10:50:16 -0700 Randy Dunlap wrote:
>> 
>> > On Fri, 30 Apr 2010 16:35:38 +1000 Stephen Rothwell wrote:
>> > 
>> > > Hi all,
>> > > 
>> > > Changes since 20100429:
>> > 
>> > 
>> > When CONFIG_SYSFS is disabled:
>> > 
>> > include/linux/sysfs.h:330: error: parameter 1 ('type') has incomplete type
>> 
>> 
>> Still have this in linux-next of May 5-2010.
>
> Eric, this is due to your changes, care to fix it up?

Apologies for not looking at this earlier.  I just took a look
at this and I believe this error is the result of a gcc bug.


This appears to the fragment that doesn't compile.

enum kobj_ns_type;
static inline void sysfs_exit_ns(enum kobj_ns_type type, const void *tag)
{
}


I could either include kobject.h or make the fragment:
static inline void sysfs_exit_ns(int type, const void *tag)
{
}

I really don't like either option. 

Does anyone know how to smack gcc up the side of the head and convince
it has all of the information it needs, and get it to stop complaining?


Eric
--
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/