On Mon, Mar 04, 2024 at 11:03:24AM +0530, Ritesh Harjani wrote: > Dave Chinner <david@xxxxxxxxxxxxx> writes: > > > On Sat, Mar 02, 2024 at 01:12:00PM +0530, Ritesh Harjani (IBM) wrote: > >> This adds direct-io atomic writes support in iomap. This adds - > >> 1. IOMAP_ATOMIC flag for iomap iter. > >> 2. Sets REQ_ATOMIC to bio opflags. > >> 3. Adds necessary checks in iomap_dio code to ensure a single bio is > >> submitted for an atomic write request. (since we only support ubuf > >> type iocb). Otherwise return an error EIO. > >> 4. Adds a common helper routine iomap_dio_check_atomic(). It helps in > >> verifying mapped length and start/end physical offset against the hw > >> device constraints for supporting atomic writes. > >> > >> This patch is based on a patch from John Garry <john.g.garry@xxxxxxxxxx> > >> which adds such support of DIO atomic writes to iomap. > > Please note this comment above. I will refer this in below comments. > > >> > >> Co-developed-by: Ojaswin Mujoo <ojaswin@xxxxxxxxxxxxx> > >> Signed-off-by: Ojaswin Mujoo <ojaswin@xxxxxxxxxxxxx> > >> Signed-off-by: Ritesh Harjani (IBM) <ritesh.list@xxxxxxxxx> > >> --- > >> fs/iomap/direct-io.c | 75 +++++++++++++++++++++++++++++++++++++++++-- > >> fs/iomap/trace.h | 3 +- > >> include/linux/iomap.h | 1 + > >> 3 files changed, 75 insertions(+), 4 deletions(-) > > > > Ugh. Now we have two competing sets of changes to bring RWF_ATOMIC > > support to iomap. One from John here: > > Not competing changes (and neither that was the intention). As you see I have > commented above saying that this patch is based on a previous patch in > iomap from John. That's not the same as co-ordinating development or collaboration on common aspects of the functionality required. > So why did I send this one? > 1. John's latest patch series v5 was on "block atomic writes" [1], which > does not have these checks in iomap (as it was not required). > > 2. For sake of completeness for ext4 atomic write support, I needed to > include this change along with this series. I have also tried to address all > the review comments he got on [2] (along with an extra function iomap_dio_check_atomic()) > > [1]: https://lore.kernel.org/all/20240226173612.1478858-1-john.g.garry@xxxxxxxxxx/ > [2]: https://lore.kernel.org/linux-fsdevel/20240124142645.9334-1-john.g.garry@xxxxxxxxxx/ Yes, but you've clearly not seen the feedback that John has been given because otherwise you would not have implemented things the way you did. That's my point - you're operating in isolation, and forcing reviewers now to deal with two separate patch sets with overlapping funcitonality and similar problems. > > https://lore.kernel.org/linux-fsdevel/20240124142645.9334-1-john.g.garry@xxxxxxxxxx/ > > > > and now this one. > > > > Can the two of you please co-ordinate your efforts and based your > > filesysetm work off the same iomap infrastructure changes? > > Sure Dave, make sense. But we are cc'ing each other in this effort > together so that we are aware of what is being worked upon. "ccing each other" is not the same as actively collaborating on development. > And as I mentioned, this change is not competing with John's change. If > at all it is only complementing his initial change, since this iomap change > addresses review comments from others on the previous one and added one > extra check (on mapped physical extent) which I wanted people to provide feedback on. > > > > > ..... > > > >> @@ -356,6 +360,11 @@ static loff_t iomap_dio_bio_iter(const struct iomap_iter *iter, > >> if (need_zeroout) { > >> /* zero out from the start of the block to the write offset */ > >> pad = pos & (fs_block_size - 1); > >> + if (unlikely(pad && atomic_write)) { > >> + WARN_ON_ONCE("pos not atomic write aligned\n"); > >> + ret = -EINVAL; > >> + goto out; > >> + } > > > > This atomic IO should have been rejected before it even got to > > the layers where the bios are being built. If the IO alignment is > > such that it does not align to filesystem allocation constraints, it > > should be rejected at the filesystem ->write_iter() method and not > > even get to the iomap layer. > > I had added this mainly from iomap sanity checking perspective. > We are offloading some checks to be made by the filesystem before > submitting the I/O request to iomap. > These "common" checks in iomap layer are mainly to provide sanity checking > to make sure FS did it's job, before iomap could form/process the bios and then > do submit_bio to the block layer. If you read the feedback John had been given, you'd know that alignment verification for atomic writes belongs in the filesystem before it even calls into iomap. See these two patches in the XFS series he just sent out: https://lore.kernel.org/linux-xfs/20240304130428.13026-11-john.g.garry@xxxxxxxxxx/T/#u https://lore.kernel.org/linux-xfs/20240304130428.13026-14-john.g.garry@xxxxxxxxxx/T/#u > > ..... > > > >> @@ -516,6 +535,44 @@ static loff_t iomap_dio_iter(const struct iomap_iter *iter, > >> } > >> } > >> > >> +/* > >> + * iomap_dio_check_atomic: DIO Atomic checks before calling bio submission. > >> + * @iter: iomap iterator > >> + * This function is called after filesystem block mapping and before bio > >> + * formation/submission. This is the right place to verify hw device/block > >> + * layer constraints to be followed for doing atomic writes. Hence do those > >> + * common checks here. > >> + */ > >> +static bool iomap_dio_check_atomic(struct iomap_iter *iter) > >> +{ > >> + struct block_device *bdev = iter->iomap.bdev; > >> + unsigned long long map_len = iomap_length(iter); > >> + unsigned long long start = iomap_sector(&iter->iomap, iter->pos) > >> + << SECTOR_SHIFT; > >> + unsigned long long end = start + map_len - 1; > >> + unsigned int awu_min = > >> + queue_atomic_write_unit_min_bytes(bdev->bd_queue); > >> + unsigned int awu_max = > >> + queue_atomic_write_unit_max_bytes(bdev->bd_queue); > >> + unsigned long boundary = > >> + queue_atomic_write_boundary_bytes(bdev->bd_queue); > >> + unsigned long mask = ~(boundary - 1); > >> + > >> + > >> + /* map_len should be same as user specified iter->len */ > >> + if (map_len < iter->len) > >> + return false; > >> + /* start should be aligned to block device min atomic unit alignment */ > >> + if (!IS_ALIGNED(start, awu_min)) > >> + return false; > >> + /* If top bits doesn't match, means atomic unit boundary is crossed */ > >> + if (boundary && ((start | mask) != (end | mask))) > >> + return false; > >> + > >> + return true; > >> +} > > > > I think you are re-implementing stuff that John has already done at > > higher layers and in a generic manner. i.e. > > generic_atomic_write_valid() in this patch: > > > > https://lore.kernel.org/linux-fsdevel/20240226173612.1478858-4-john.g.garry@xxxxxxxxxx/ > > > > We shouldn't be getting anywhere near the iomap layer if the IO is > > not properly aligned to atomic IO constraints... > > So current generic_atomic_write_valid() function mainly checks alignment > w.r.t logical offset and iter->len. > > What this function was checking was on the physical block offset and > mapped extent length. Hence it was made after iomap_iter() call. > i.e. ... The filesystem is supposed to guarantee the alignment of the iomap returned for mapping requests on inodes configured for atomic writes. IOWs, if the filesystem returns an unaligned or short extent for an atomic write enabled inode, the filesystem mapping operation is buggy. If it can't map aligned extents, then it should return an error, not leave crap for the iomap infrastructure to have to clean up. > > + /* map_len should be same as user specified iter->len */ > + if (map_len < iter->len) > + return false; > + /* start should be aligned to block device min atomic unit alignment */ > + if (!IS_ALIGNED(start, awu_min)) > + return false; > > > But I agree, that maybe we can improve generic_atomic_write_valid() > to be able to work on both logical and physical offset and > iter->len + mapped len. > Let me think about it. > > However, the point on which I would like a feedback from others is - > 1. After filesystem has returned the mapped extent in iomap_iter() call, > iomap will be forming a bio to be sent to the block layer. > So do we agree to add a check here in iomap layer to verify that the > mapped physical start and len should satisfy the requirements for doing > atomic writes? That's entirely the problem about you working on this in isolation: we've already had that discussion and the simplest solution is that this is a filesystem problem, not an iomap problem. That is, if the filesystem cannot return a correctly aligned and sized extent for an atomic write enabled inode, it must return an error and not a malformed iomap. IOWs, it's not the job of the iomap IO routines to enforce mapping alignment on these inodes - the extent alignment must always be correct for atomic writes regardless of whether an atomic write IO is being done or not. Failure to align any extent in the inode correctly will result in future atomic writes to that offset being impossible to issue. Hence if the inode is configured for atomic writes, it *must* return aligned and sized iomaps that atomic writes can be issued against. It's a filesystem implementation bug if this invariant is violated, so the filesystem implementation is where all the debug checks need to be to ensure it never returns an invalid mapping to the iomap infrastructure. -Dave. -- Dave Chinner david@xxxxxxxxxxxxx
