linux-kernel - Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2

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:	Tue, 07 Aug 2007 11:43:45 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	James Bottomley <James.Bottomley@...elEye.com>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-scsi <linux-scsi@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PATCH] scsi bug fixes for 2.6.23-rc2

James Bottomley wrote:
> It followed the rule of trying to stabilise outside mainline ... it just
> didn't get sufficient integration testing.

IMO it's self-evident that pushing to a git tree few ever see or test is 
not following the spirit of the rule.

In practice, stabilize outside mainline implies -mm integration, in 
addition to whatever else a maintainer does specific to their subsystem.


>>> I wouldn't call bsg half baked ... it was very carefully matured.  There
>>> were just a few integration issues.
>> I wouldn't call bsg carefully matured, if in addition to not really 
>> gracing -mm with its presence, the userland API structure is still 
>> getting changes on July 29, 2007 (0c6a89ba640d28e1dcd7fd1a217d2cfb92ae4953).
> 
> This would be the ABI change I talked about in the previous emails.
> 
> So would this problem have been fixed simply by adding the missing block
> tree to -mm?

IMO 70% of the problem would be solved by that.

It wouldn't have solved the late ABI change though (which was first 
posted in earlier form on April 4th, and so, had time for integration).

	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/