linux-kernel - Re: linux-next: Tree for June 3 (driver core)

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: <20090603212206.GA20804@suse.de>
Date:	Wed, 3 Jun 2009 14:22:06 -0700
From:	Greg KH <gregkh@...e.de>
To:	Randy Dunlap <randy.dunlap@...cle.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for June 3 (driver core)

On Wed, Jun 03, 2009 at 08:50:10AM -0700, Randy Dunlap wrote:
> Stephen Rothwell wrote:
> > Hi all,
> > 
> > Looks like a real rush since -rc7 ...
> 
> 
> drivers/built-in.o: In function `register_mem_sect_under_node':
> (.text+0x1d305b): undefined reference to `sysfs_create_link_nowarn'
> 
> 
> I can't find this function's implementation when CONFIG_SYSFS=y.

Ah, it looks like this shows up when CONFIG_MEMORY_HOTPLUG_SPARSE is
set.

Eric, your patch, "sysfs: Remove now unnecessary error reporting
suppression." caused this.  Turns out it is still used in the tree, and
you forgot to remove the function from sysfs.h at the same time.

I'm going to drop it, and the other two patches I took from you for
sysfs, as it doesn't make sense to have them in the tree yet.

Care to rework your series with this fixed?

thanks,

greg k-h
--
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/