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]

Date:	Thu, 26 Oct 2006 19:11:31 -0700
From:	Stephen Hemminger <shemminger@...l.org>
To:	Andrew Morton <akpm@...l.org>
Cc:	Matthew Wilcox <matthew@....cx>, Adrian Bunk <bunk@...sta.de>,
	Linus Torvalds <torvalds@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Pavel Machek <pavel@....cz>, Greg KH <greg@...ah.com>,
	linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: [RFC: 2.6.19 patch] let PCI_MULTITHREAD_PROBE depend on BROKEN

On Thu, 26 Oct 2006 18:28:38 -0700
Andrew Morton <akpm@...l.org> wrote:

> On Thu, 26 Oct 2006 19:20:58 -0600
> Matthew Wilcox <matthew@....cx> 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.
> 
> It's not the impact on "people" which is of concern - it's the impact on
> kernel developers - specifically those who spend time looking at bug
> reports :(

Either it is broken and should be removed, or is barely working and
should be fixed. If Greg wants to take bug reports then it can stay.
-
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/