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] [day] [month] [year] [list]

Message-ID: <20070813180757.GZ23758@kernel.dk>
Date:	Mon, 13 Aug 2007 20:07:57 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	James Bottomley <James.Bottomley@...elEye.com>,
	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

On Mon, Aug 13 2007, Jens Axboe wrote:
> On Mon, Aug 13 2007, Jeff Garzik wrote:
> > Jens Axboe wrote:
> > >#for-akpm is usually only in very few -mm release anyway, so it's not
> > >like it would have made much difference. We/you/I need to improve that,
> > >certainly.
> > >
> > >Honestly, for bsg, it wasn't much of an issue. We had build problems
> > >when bsg was merged which was unfortunate but got fixed quickly. Having
> > >bsg in -mm would not have caused any testing of the driver in question
> > >outside of what it already received, given the nature of it.
> > 
> > 
> > That's just an excuse for what happened -- you made an end run around 
> > our test tree.  Pretty please with sugar on it -- make sure changes show 
> > up in -mm.
> 
> It's not just an excuse, there are repeatably problems with getting the
> block stuff pulled into -mm. Sometimes it's my problem, but not always.
> Then I get a note saying that pulling was disabled due to merge
> problems, usually right before -mmX goes out. So it misses that release.

This may sound like I'm blaming Andrew, but that is not my intention. He
does a lot of work and he can't (and should not) attempt to fix every
integration and merge issue. Perhaps if I/we were more strict in pushing
every block bit through the block git tree, it wouldn't be so much of an
integration pain. Then the work would be in me to sort out, which I'm
happy to do.

Then there are things like the sg chaining bits, which touch a lot of
arch code. Those are just painful to deal with, for obvious reasons.
Right now there are not in -mm, but that's because of a bug that
prevents Andrews laptop from booting properly.

-- 
Jens Axboe

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