linux-kernel - Re: Persistent Reservation API

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 4 Aug 2015 13:53:49 -0400
From:	Mike Snitzer <snitzer@...hat.com>
To:	Christoph Hellwig <hch@....de>
Cc:	Jens Axboe <axboe@...com>, linux-api@...r.kernel.org,
	dm-devel@...hat.com, linux-nvme@...ts.infradead.org,
	linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Persistent Reservation API

On Tue, Aug 04 2015 at  3:11am -0400,
Christoph Hellwig <hch@....de> wrote:

> This series adds support for a simplified persistent reservation API
> to the block layer.  The intent is that both in-kernel and userspace
> consumers can use the API instead of having to hand craft SCSI or NVMe
> command through the various pass through interfaces.  It also adds
> DM support as getting reservations through dm-multipath is a major
> pain with the current scheme.

The DM changes need to go through linux-dm.git.  Once the block and SCSI
bits land I'll rebase accordingly.  That cross-maintainer logisitics
aside, I'll reply with feedback on the DM patches.
--
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/