linux-kernel - Re: 2.6.19-rc3-mm1 -- missing network adaptors

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:	Mon, 30 Oct 2006 23:30:01 -0800
From:	"Martin J. Bligh" <mbligh@...gle.com>
To:	Greg KH <gregkh@...e.de>
CC:	Mike Galbraith <efault@....de>,
	Cornelia Huck <cornelia.huck@...ibm.com>,
	Andy Whitcroft <apw@...dowen.org>,
	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	Steve Fox <drfickle@...ibm.com>
Subject: Re: 2.6.19-rc3-mm1 -- missing network adaptors

Greg KH wrote:
> On Mon, Oct 30, 2006 at 10:37:47PM -0800, Martin J. Bligh wrote:
>> Mike Galbraith wrote:
>>> On Mon, 2006-10-30 at 21:14 +0100, Cornelia Huck wrote:
>>>
>>>> Maybe the initscripts have problems coping with the new layout
>>>> (symlinks instead of real devices)?
>>> SuSE's /sbin/getcfg for one uses libsysfs, which apparently doesn't
>>> follow symlinks (bounces off symlink and does nutty stuff instead).  If
>>> any of the boxen you're having troubles with use libsysfs in their init
>>> stuff, that's likely the problem.
>> If that is what's happening, then the problem is breaking previously
>> working boxes by changing a userspace API. I don't know exactly which
>> patch broke it, but reverting all Greg's patches (except USB) from
>> -mm fixes the issue.
> 
> Merely change CONFIG_SYSFS_DEPRECATED to be set to yes, and it should
> all work just fine.  Doesn't anyone read the Kconfig help entries for
> new kernel options?

1. This doesn't fix it.
2. Breaking things by default with an option to unbreak them is not
the finest of plans ;-)

M.
-
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/