gfs2: Explain some direct I/O oddities

Add some comments explaining the oddities of partial direct I/O reads
and writes.

Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>

diff --git a/fs/gfs2/file.c b/fs/gfs2/file.c
index 2556ae1f92ea2d9e27d0fefe9c60c09543c6c563..f1d2f4d74b898d62d48114f18d8711ff46d3fcc5 100644 (file)
--- a/fs/gfs2/file.c
+++ b/fs/gfs2/file.c
@@ -840,6 +840,7 @@ retry:
        pagefault_enable();
        if (ret <= 0 && ret != -EFAULT)
                goto out_unlock;
+       /* No increment (+=) because iomap_dio_rw returns a cumulative value. */
        if (ret > 0)
                read = ret;
 
@@ -854,6 +855,7 @@ out_unlock:
                gfs2_glock_dq(gh);
 out_uninit:
        gfs2_holder_uninit(gh);
+       /* User space doesn't expect partial success. */
        if (ret < 0)
                return ret;
        return read;
@@ -906,6 +908,7 @@ retry:
                if (ret != -EFAULT)
                        goto out_unlock;
        }
+       /* No increment (+=) because iomap_dio_rw returns a cumulative value. */
        if (ret > 0)
                written = ret;
 
@@ -920,6 +923,7 @@ out_unlock:
                gfs2_glock_dq(gh);
 out_uninit:
        gfs2_holder_uninit(gh);
+       /* User space doesn't expect partial success. */
        if (ret < 0)
                return ret;
        return written;