[dm-devel] [PATCH v3 01/10] dm-table: Introduce DM_TARGET_ZONED_HM feature

From: Damien Le Moal The target drivers currently available will not operate correctly if a table target maps onto a host-managed zoned block device. To avoid problems, this patch introduces the new feature flag DM_TARGET_ZONED_HM for a target driver to explicitly state

Re: [dm-devel] remove REQ_OP_WRITE_SAME

Christoph, > Any chance to get a sneak preview of that work? I have been on the road since LSF/MM and just got back home. I'll make it a priority. -- Martin K. Petersen Oracle Linux Engineering -- dm-devel mailing list dm-devel@redhat.com https://www.redhat.com/mailman/listinfo/dm-devel

[dm-devel] [PATCH v3 05/10] dm: Fix REQ_OP_ZONE_REPORT bio handling

From: Damien Le Moal A REQ_OP_ZONE_REPORT bio is not a medium access command. Its number of sectors indicates the maximum size allowed for the report reply size and not an amount of sectors accessed from the device. REQ_OP_ZONE_REPORT bios should thus not be split

[dm-devel] [PATCH v3 10/10] dm-zoned: Drive-managed zoned block device target

From: Damien Le Moal The dm-zoned device mapper target provides transparent write access to zoned block devices (ZBC and ZAC compliant block devices). dm-zoned hides to the device user (a file system or an application doing raw block device accesses) any constraint imposed

[dm-devel] [PATCH v3 06/10] dm: Introduce dm_remap_zone_report()

From: Damien Le Moal A target driver support zoned block devices and exposing it as such may receive REQ_OP_ZONE_REPORT request for the user to determine the mapped device zone configuration. To process properly such request, the target driver may need to remap the zone

[dm-devel] [PATCH v3 08/10] dm-linear: Add support for zoned block devices

From: Damien Le Moal Add support for zoned block devices by allowing host-managed zoned block device mapped targets, the remapping of REQ_OP_ZONE_RESET and the post processing (reply remapping) of REQ_OP_ZONE_REPORT. Signed-off-by: Damien Le Moal

[dm-devel] [PATCH v3 02/10] dm-table: Check device area zone alignment

From: Damien Le Moal If a target maps to a zoned block device, check that the device area is aligned on zone boundaries to avoid problems with REQ_OP_ZONE_RESET operations (resetting a partially mapped sequential zone would not be possible). This also greatly facilitate

[dm-devel] [PATCH v3 03/10] dm-table: Check block devices zone model compatibility

From: Damien Le Moal When setting the dm device queue limits, several possibilities exists for zoned block devices: 1) The dm target driver may want to expose a different zone model (e.g. host-managed device emulation or regular block device on top of host-managed zoned

[dm-devel] [PATCH v3 04/10] dm: Fix REQ_OP_ZONE_RESET bio handling

From: Damien Le Moal The REQ_OP_ZONE_RESET bio has no payload and zero sectors. Its position is the only information used to indicate the zone to reset on the device. Due to its zero length, this bio is not cloned and sent to the target through the non-flush case in

[dm-devel] [PATCH v3 00/10] dm: zoned block device support

From: Damien Le Moal [ Note: I'm resending this patch series on Damien's behalf because Damien's ] [ e-mails apparently do not reach the dm-devel mailing list - Bart. ] This series introduces zoned block device support to the device mapper infrastructure. Pathces

Re: [dm-devel] [PATCH 00/10] fixes for kpartx -d

On Sat, May 06, 2017 at 12:05:49AM +0200, Martin Wilck wrote: > Working on a bug report about kpartx not properly removing > partitions for loop devices, I realized a number of glitches > and improperly handled corner cases in the kpartx code for > deleting partitions. Some mappings are not

Re: [dm-devel] [PATCH 02/10] kpartx: avoid ioctl error for loop devices

dm_no_partitions() checks if features includes "no_partitions", but the upstream kernel doesn't allow that feature. The patch to add it got NAKed when Hannes posted it, IIRC. That's why I went the route of using udev flags to avoid running kpartx. Unless SUSE (or some other distro) is using the

Re: [dm-devel] [PATCH 08/10] kpartx: use partition UUID for non-DM devices

On Fri, 2017-05-05 at 23:30 +0100, Alasdair G Kergon wrote: > On Sat, May 06, 2017 at 12:05:57AM +0200, Martin Wilck wrote: > > Introduce a "fake" UUID for these devices to make sure kpartx > > deletes only devices it had created previously. Otherwise kpartx > > might e.g. delete LVM LVs that are

Re: [dm-devel] [PATCH 00/10] fixes for kpartx -d

On Mon, 2017-05-08 at 09:47 +0200, Martin Wilck wrote: > The full partition UUID for partitions used by my code looks like > this > (see patch 08/10): > > {UUID_PREFIX}${MAJOR}:${MINOR}-${NONDM_UUID_SUFFIX}" ... where UUID_PREFIX is what kpartx uses anyway, i.e. "part$N". Martin -- Dr. Martin

Re: [dm-devel] [PATCH 00/10] fixes for kpartx -d

On 05/06/2017 12:30 AM, Martin Wilck wrote: > On Fri, 2017-05-05 at 23:18 +0100, Alasdair G Kergon wrote: >> On Sat, May 06, 2017 at 12:05:49AM +0200, Martin Wilck wrote: >>> 3) kpartx should only delete "partitions", which are single- >>> target >>> linear mappings into a block device.