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]

Message-ID: <45478E2C.7020803@shadowen.org>
Date:	Tue, 31 Oct 2006 17:55:56 +0000
From:	Andy Whitcroft <apw@...dowen.org>
To:	Cornelia Huck <cornelia.huck@...ibm.com>
CC:	"Martin J. Bligh" <mbligh@...gle.com>, Greg KH <gregkh@...e.de>,
	Mike Galbraith <efault@....de>, 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

Cornelia Huck wrote:
> On Tue, 31 Oct 2006 09:09:16 -0800,
> "Martin J. Bligh" <mbligh@...gle.com> wrote:
> 
>> Cornelia Huck wrote:
>>> That's because /sys/class/net/<interface> is now a symlink instead of a
>>> directory (and that hasn't anything to do with acpi, but rather with
>>> the conversions in the driver tree). Seems the directory -> symlink
>>> change shouldn't be done since it's impacting user space...
>> You know which individual patch in -mm broke that? Can't see it easily.
>> Then we can just test across all the machines with just that one backed
>> out.
> 
> I'd try reverting gregkh-driver-network-device.patch for the network
> device stuff.

Ok, I've done a bisection which came back to:

    gregkh-driver-mem-devices

But as it seems somewhat nonsensical I'll submit two tests one with that
backed out and one with the patch below backed out:

    gregkh-driver-network-device

Results should be out on TKO in a few hours.  Will report back tommorrow
in detail.

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