linux-kernel - Re: 2.6.20-rc2: known unfixed regressions

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, 28 Dec 2006 15:17:53 -0800 (PST)
From:	Linus Torvalds <torvalds@...l.org>
To:	Adrian Bunk <bunk@...sta.de>
cc:	Greg KH <gregkh@...e.de>, Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ben Castricum <mail0612@...castricum.nl>,
	linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: 2.6.20-rc2: known unfixed regressions

On Fri, 29 Dec 2006, Adrian Bunk wrote:
> 
> In Linus' tree, it currently only depends on EXPERIMENTAL.
> 
> It seems commit 009af1ff78bfc30b9a27807dd0207fc32848218a wasn't intended 
> for Linus?

I think we should just remove it.

It's broken.

Nobody cares.

If people want to do concurrent stuff at bootup, it should be the _other_ 
buses (like USB, IDE or SCSI or anything like that, that actually has 
operations that can delay) that end up asynchronous. And I think we could 
have some generic functionality for the drivers themselves to do their 
probing in parallel. But I think the PCI one was just a mistake.

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