diff options
author | 2025-03-20 12:02:50 +0000 | |
---|---|---|
committer | 2025-03-20 15:16:03 +0100 | |
commit | 370a6de7651b9745b997c32f90685f9e100ccfcd (patch) | |
tree | 4d4b795d790bc75732732b86d2fee16548ec1666 /mm/util.c | |
parent | iomap: comment on atomic write checks in iomap_dio_bio_iter() (diff) | |
download | wireguard-linux-370a6de7651b9745b997c32f90685f9e100ccfcd.tar.xz wireguard-linux-370a6de7651b9745b997c32f90685f9e100ccfcd.zip |
iomap: rework IOMAP atomic flags
Flag IOMAP_ATOMIC_SW is not really required. The idea of having this flag
is that the FS ->iomap_begin callback could check if this flag is set to
decide whether to do a SW (FS-based) atomic write. But the FS can set
which ->iomap_begin callback it wants when deciding to do a FS-based
atomic write.
Furthermore, it was thought that IOMAP_ATOMIC_HW is not a proper name, as
the block driver can use SW-methods to emulate an atomic write. So change
back to IOMAP_ATOMIC.
The ->iomap_begin callback needs though to indicate to iomap core that
REQ_ATOMIC needs to be set, so add IOMAP_F_ATOMIC_BIO for that.
These changes were suggested by Christoph Hellwig and Dave Chinner.
Signed-off-by: John Garry <john.g.garry@oracle.com>
Link: https://lore.kernel.org/r/20250320120250.4087011-4-john.g.garry@oracle.com
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'mm/util.c')
0 files changed, 0 insertions, 0 deletions