Yeah, ->iomap_begin can't directly look at the iocb.would make the core iomap code set REQ_ATOMIC on the bio for thatbut we still need to tell ->iomap_begin about IOCB_ATOMIC, hence
iteration.
IOMAP_DIO_BIO_ATOMIC which sets IOMAP_BIO_ATOMIC.Well, I'd imagine __iomap_dio_rw just sets IOMAP_ATOMIC from IOCB_ATOMIC
We can't allow __iomap_dio_rw() check IOCB_ATOMIC only (and set
IOMAP_BIO_ATOMIC), as this is the common path for COW and regular atomic
write
and then it's up to file system internal state if it wants to set
IOMAP_F_REQ_ATOMIC based on that, i.e. the actual setting of
IOMAP_F_REQ_ATOMIC is fully controlled by the file system and not
by the iomap core.