linux-kernel - Re: [patch 07/69] libata-sff: Undo bug introduced with pci

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: <46522C37.1020404@garzik.org>
Date:	Mon, 21 May 2007 19:33:11 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Chris Wright <chrisw@...s-sol.org>, linux-kernel@...r.kernel.org,
	stable@...nel.org, Tejun Heo <htejun@...il.com>,
	Justin Forbes <jmforbes@...uxtx.org>,
	Zwane Mwaikambo <zwane@....linux.org.uk>,
	Theodore Ts'o <tytso@....edu>,
	Randy Dunlap <rdunlap@...otime.net>,
	Dave Jones <davej@...hat.com>,
	Chuck Wolber <chuckw@...ntumlinux.com>,
	Chris Wedgwood <reviews@...cw.f00f.org>,
	Michael Krufky <mkrufky@...uxtv.org>,
	Chuck Ebbert <cebbert@...hat.com>, akpm@...ux-foundation.org,
	alan@...rguk.ukuu.org.uk, Alan Cox <alan@...hat.com>
Subject: Re: [patch 07/69] libata-sff: Undo bug introduced with pci_iomap
 changes

Linus Torvalds wrote:
> 
> On Mon, 21 May 2007, Chris Wright wrote:
>> ---
>> [chrisw: Why is this not upstream yet?]
> 
> And equally importantly, why is it even in the stable queue if it's not 
> upstream.
> 
> It's against stable rules, and it means that we may have stuff that gets 
> fixed in -stable and not in -upstream, if people don't notice. THAT IS 
> BAD!
> 
> Having fixes in stable that don't exist in upstream make -stable be 
> worse than pointless - it means that we actively _lose_ bug-reports. It 
> may sound like a good idea in the short run, but it's a *horrible* thing 
> for the long run.
> 
> IOW, this should not be on the table for -stable, and people involved 
> should have made sure it's in -upstream first!

Strongly agreed.


> And no, I do not think it's languishing in my mailqueue. I'm pretty sure 
> it's languishing somewhere else. 

AFAIK it was obsoleted by another Tejun patch which -is- upstream.

Am I missing something?

	Jeff



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