linux-kernel - Re: Nonfunctional ethernet (was Re: 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch -- INFO: possible recursive locking detected)

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:	Thu, 26 Apr 2007 11:26:36 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
CC:	"Antonino A. Daplas" <adaplas@...il.com>,
	Miles Lane <miles.lane@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Nonfunctional ethernet (was Re: 2.6.21-rc7-mm1 + sysfs-oops-workaround.patch
 -- INFO: possible recursive locking detected)

Hello, Antonino, Andrew.

Andrew Morton wrote:
> On Thu, 26 Apr 2007 09:02:02 +0800 "Antonino A. Daplas" <adaplas@...il.com> wrote:
> 
>> I can bring up the network manually using ifconfig.  It's opensuse's
>> rcnetwork script that fails to bring the network up. Entries
>> in /sys/class/net are still bogus.
>>
>> This kernel is now usable to me, I'll start bisection later today if
>> nobody has an answer.
> 
> rc7-mm1 is hardly worth bothering with.  Quite a few really bad ones have
> now been fixed and I'll try to get rc7-mm2 out within the next 12 hours (I
> assume a 76-hour debug session won't be needed this time).
> 
> But I don't think the sysfs changes in Greg's tree have been updated, so
> things will probably still fail in that area.  A suitable bisection
> starting pair would be around gregkh-driver-*

This is the rename bug I wrote about in the other thread.  Can you hold
-mm2 off a bit?  I'm almost done here.

Thanks.

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