linux-kernel - Re: remove exofs, the T10 OSD code and block/scsi bidi support V4

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: <20190205171628.GA2129@lst.de>
Date:   Tue, 5 Feb 2019 18:16:28 +0100
From:   Christoph Hellwig <hch@....de>
To:     Boaz Harrosh <ooo@...ctrozaur.com>
Cc:     Christoph Hellwig <hch@....de>, axboe@...nel.dk,
        martin.petersen@...cle.com,
        Johannes Thumshirn <jthumshirn@...e.de>,
        Benjamin Block <bblock@...ux.vnet.ibm.com>,
        linux-scsi@...r.kernel.org, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: remove exofs, the T10 OSD code and block/scsi bidi support V4

On Mon, Feb 04, 2019 at 10:31:39PM +0200, Boaz Harrosh wrote:
> On 01/02/19 09:55, Christoph Hellwig wrote:
> > The only real user of the T10 OSD protocol, the pNFS object layout
> > driver never went to the point of having shipping products, and we
> > removed it 1.5 years ago.  Exofs is just a simple example without
> > real life users.
> > 
> > The code has been mostly unmaintained for years and is getting in the
> > way of block / SCSI changes, 
> 
> For the 4th time: Which ?

Speeding up the I/O path for example.  Making sense of SCSI
command allocation for another.  Having to deal with sense data
handling for the duplicate scsi command allocation as a third.