linux-kernel - Re: state of the osdblk 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]

Message-ID: <CAFtxgO5cPNTMqyY5Foqp_Y+pqCH=zTiatREn-4xRCTm8o5GLwA@mail.gmail.com>
Date:	Tue, 21 Oct 2014 08:21:13 -0400
From:	Jeff Garzik <jgpobox@...il.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Boaz Harrosh <ooo@...ctrozaur.com>,
	Jeff Garzik <jgarzik@...ox.com>,
	Kernel development list <linux-kernel@...r.kernel.org>,
	osd-dev@...n-osd.org
Subject: Re: state of the osdblk driver?

Drop it, if there are no users.

It was simulating an OSD, but there did not seem to be much beyond
academic interest, and some interest in the use of aforementioned
block functions as a useful exercise in block driver writing.


On Tue, Oct 21, 2014 at 8:06 AM, Christoph Hellwig <hch@...radead.org> wrote:
> The osdblk driver hsa seen literally no change except for global
> API changes since it was merged, and I've never heard of a user.
>
> Is this something we want to keep around?  I just noticed it because
> it's the only non-SCSI user of some of the old block layer tagging
> functions.
--
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/