linux-kernel - Re: [PATCH] Promise 'stex' driver

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:	Fri, 21 Jul 2006 03:06:22 +0200
From:	Jens Axboe <axboe@...e.de>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Ed Lin <ed.lin@...mise.com>,
	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	"James.Bottomley" <James.Bottomley@...elEye.com>,
	hch <hch@...radead.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	akpm <akpm@...l.org>, promise_linux <promise_linux@...mise.com>
Subject: Re: [PATCH] Promise 'stex' driver

On Thu, Jul 20 2006, Jeff Garzik wrote:
> 5) [agreement/correction]  The block tagging API supports adapter-wide
> tags just fine.  HOWEVER, I nonetheless feel that block tagging API use
> should be considered post-merge.  The 'stex' driver is working and
> tested today.  Since _no individual SCSI driver_ uses the block layer
> tagging, it is likely that some instability and core kernel development
> will occur, in order to make that work.

I'd disagree. If the driver gets merged with the current tagging, I'll
get you two beers that it never gets changed.

And you are wrong, block layer tagging is used by at least one SCSI
driver. We definitely need to start pushing it more.

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