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).
Showing the changes to include/uapi/linux (1 of 3 files). Show all
Unified · Split
| @@ -286,9 +286,9 @@ enum { · 285 unmodified lines | ||
| 286 | 286 | #define DM_DEV_SET_GEOMETRY _IOWR(DM_IOCTL, DM_DEV_SET_GEOMETRY_CMD, struct dm_ioctl) |
| 287 | 287 | |
| 288 | 288 | #define DM_VERSION_MAJOR 4 |
| 289 | −#define DM_VERSION_MINOR 48 | |
| 289 | +#define DM_VERSION_MINOR 49 | |
| 290 | 290 | #define DM_VERSION_PATCHLEVEL 0 |
| 291 | −#define DM_VERSION_EXTRA "-ioctl (2023-03-01)" | |
| 291 | +#define DM_VERSION_EXTRA "-ioctl (2025-01-17)" | |
| 292 | 292 | |
| 293 | 293 | /* Status bits */ |
| 294 | 294 | #define DM_READONLY_FLAG (1 << 0) /* In/Out */ |