linux-kernel - Re: Linux 2.6.21-rc1

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, 21 Feb 2007 07:58:36 -0800
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	tglx@...utronix.de
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jeff Garzik <jeff@...zik.org>,
	Arjan van de Ven <arjan@...ux.intel.com>
Subject: Re: Linux 2.6.21-rc1

Thomas Gleixner wrote:
> On Tue, 2007-02-20 at 20:53 -0800, Linus Torvalds wrote:
>> But there's a ton of architecture updates (arm, mips, powerpc, x86, you 
>> name it), ACPI updates, and lots of driver work. And just a lot of 
>> cleanups.
>>
>> Have fun,
> 
> Yup. Fun starts in drivers/net/e1000
> 
> e1000 is not working anymore. ifup fails permanentely.
>  ADDRCONF(NETDEV_UP): eth0: link is not ready
> nothing else
> 
> bisect identifies:
> 
> d2ed16356ff4fb9de23fbc5e5d582ce580390106 is first bad commit
 > commit d2ed16356ff4fb9de23fbc5e5d582ce580390106

I think we need to drop this now. The report that says that this *fixes* 
something might have been on regular interrupts only. I currently suspect that 
it breaks all MSI interrupts, which would make sense if I look a the code. Very 
bad indeed.

I'll try to come up with something else or send a patch that reverts it.

Auke

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