dm-table: atomic writes support
authorJohn Garry <john.g.garry@oracle.com>
Thu, 16 Jan 2025 17:02:56 +0000 (17:02 +0000)
committerMikulas Patocka <mpatocka@redhat.com>
Fri, 17 Jan 2025 21:23:47 +0000 (22:23 +0100)
commit3194e36488e2dae05f9a822c73eaa367e47b2e3d
treeeb2c2089c158123926c2fdfd067903421435a663
parenta38425935f7886cef5fe04c796f36715e9d0ef3f
dm-table: atomic writes support

Support stacking atomic write limits for DM devices.

All the pre-existing code in blk_stack_atomic_writes_limits() already takes
care of finding the aggregrate limits from the bottom devices.

Feature flag DM_TARGET_ATOMIC_WRITES is introduced so that atomic writes
can be enabled on personalities selectively. This is to ensure that atomic
writes are only enabled when verified to be working properly (for a
specific personality). In addition, it just may not make sense to enable
atomic writes on some personalities (so this flag also helps there).

Signed-off-by: John Garry <john.g.garry@oracle.com>
Reviewed-by: Mike Snitzer <snitzer@kernel.org>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
drivers/md/dm-table.c
include/linux/device-mapper.h
include/uapi/linux/dm-ioctl.h