linux-kernel - Re: [RFC: 2.6.19 patch] let PCI_MULTITHREAD

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: <20061027082726.GA1880@elf.ucw.cz>
Date:	Fri, 27 Oct 2006 10:27:26 +0200
From:	Pavel Machek <pavel@....cz>
To:	Matthew Wilcox <matthew@....cx>
Cc:	Adrian Bunk <bunk@...sta.de>, Linus Torvalds <torvalds@...l.org>,
	Andrew Morton <akpm@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg KH <greg@...ah.com>, linux-pci@...ey.karlin.mff.cuni.cz,
	Stephen Hemminger <shemminger@...l.org>
Subject: Re: [RFC: 2.6.19 patch] let PCI_MULTITHREAD_PROBE depend on BROKEN

On Thu 2006-10-26 19:20:58, Matthew Wilcox wrote:
> On Fri, Oct 27, 2006 at 03:02:52AM +0200, Adrian Bunk wrote:
> > PCI_MULTITHREAD_PROBE is an interesting feature, but in it's current 
> > state it seems to be more of a trap for users who accidentally
> > enable it.
> > 
> > This patch lets PCI_MULTITHREAD_PROBE depend on BROKEN for 2.6.19.
> > 
> > The intention is to get this patch reversed in -mm as soon as it's in 
> > Linus' tree, and reverse it for 2.6.20 or 2.6.21 after the fallout of 
> > in-kernel problems PCI_MULTITHREAD_PROBE causes got fixed.
> 
> People who enable features clearly marked as EXPERIMENTAL deserve what
> they get, IMO.

Eh? It is no longer "experimental". It went to "known broken in
non-funny ways".

People normally use experimental features... (like cpu hotplug, acpi
hotkeys, intel 830m framebuffer, USB CATC ethernet, SDHCI, kernel
profiling) without expecting breakages. (Hmm, perhaps some of these
should not be marked experimental any more?)

I'd actually vote for removing MULTITHREAD_PROBE from kconfig,
temporarily, but I guess BROKEN is okay, too.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/