From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: John Garry <john.g.garry@oracle.com>,
brauner@kernel.org, djwong@kernel.org, hch@lst.de
Cc: linux-fsdevel@vger.kernel.org, dchinner@redhat.com,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
ojaswin@linux.ibm.com, martin.petersen@oracle.com, tytso@mit.edu,
linux-ext4@vger.kernel.org, John Garry <john.g.garry@oracle.com>
Subject: Re: [PATCH 2/3] iomap: comment on atomic write checks in iomap_dio_bio_iter()
Date: Fri, 21 Mar 2025 01:02:05 +0530 [thread overview]
Message-ID: <87ldszsdl6.fsf@gmail.com> (raw)
In-Reply-To: <20250320120250.4087011-3-john.g.garry@oracle.com>
John Garry <john.g.garry@oracle.com> writes:
> Help explain the code.
>
> Also clarify the comment for bio size check.
Looks good to me. Feel free to add:
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
>
> Signed-off-by: John Garry <john.g.garry@oracle.com>
> ---
> fs/iomap/direct-io.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/fs/iomap/direct-io.c b/fs/iomap/direct-io.c
> index 8c1bec473586..b9f59ca43c15 100644
> --- a/fs/iomap/direct-io.c
> +++ b/fs/iomap/direct-io.c
> @@ -350,6 +350,11 @@ static int iomap_dio_bio_iter(struct iomap_iter *iter, struct iomap_dio *dio)
> bio_opf |= REQ_OP_WRITE;
>
> if (iter->flags & IOMAP_ATOMIC_HW) {
> + /*
> + * Ensure that the mapping covers the full write
> + * length, otherwise it won't be submitted as a single
> + * bio, which is required to use hardware atomics.
> + */
> if (length != iter->len)
> return -EINVAL;
> bio_opf |= REQ_ATOMIC;
> @@ -449,7 +454,7 @@ static int iomap_dio_bio_iter(struct iomap_iter *iter, struct iomap_dio *dio)
> n = bio->bi_iter.bi_size;
> if (WARN_ON_ONCE((bio_opf & REQ_ATOMIC) && n != length)) {
> /*
> - * This bio should have covered the complete length,
> + * An atomic write bio must cover the complete length,
> * which it doesn't, so error. We may need to zero out
> * the tail (complete FS block), similar to when
> * bio_iov_iter_get_pages() returns an error, above.
> --
> 2.31.1
next prev parent reply other threads:[~2025-03-20 19:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 12:02 [PATCH 0/3] further iomap large atomic writes changes John Garry
2025-03-20 12:02 ` [PATCH 1/3] iomap: inline iomap_dio_bio_opflags() John Garry
2025-03-20 12:02 ` [PATCH 2/3] iomap: comment on atomic write checks in iomap_dio_bio_iter() John Garry
2025-03-20 14:09 ` Christoph Hellwig
2025-03-20 19:32 ` Ritesh Harjani [this message]
2025-03-20 12:02 ` [PATCH 3/3] iomap: rework IOMAP atomic flags John Garry
2025-03-20 14:10 ` Christoph Hellwig
2025-03-20 19:29 ` Ritesh Harjani
2025-03-22 19:47 ` Ritesh Harjani
2025-03-23 6:38 ` Christoph Hellwig
2025-03-23 13:07 ` John Garry
2025-03-23 13:42 ` Ritesh Harjani
2025-03-26 15:50 ` John Garry
2025-03-27 10:46 ` Christoph Hellwig
2025-03-20 14:16 ` [PATCH 0/3] further iomap large atomic writes changes Christian Brauner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ldszsdl6.fsf@gmail.com \
--to=ritesh.list@gmail.com \
--cc=brauner@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ojaswin@linux.ibm.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).