From: Trond Myklebust <trondmy@kernel.org>
To: Mike Snitzer <snitzer@kernel.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/4] NFS/localio: Stop further I/O upon hitting an error
Date: Mon, 05 Jan 2026 12:35:07 -0500 [thread overview]
Message-ID: <09331fd9a94cb5bb8ffa7ae4bcfc3f8f5af06def.camel@kernel.org> (raw)
In-Reply-To: <aVvyl52wfhyeNGvp@kernel.org>
On Mon, 2026-01-05 at 12:19 -0500, Mike Snitzer wrote:
> On Sat, Jan 03, 2026 at 12:14:57PM -0500, Trond Myklebust wrote:
> > From: Trond Myklebust <trond.myklebust@hammerspace.com>
> >
> > If the call into the filesystem results in an I/O error, then the
> > next
> > chunk of data won't be contiguous with the end of the last
> > successful
> > chunk. So break out of the I/O loop and report the results.
> > Currently the localio code will do this for a short read/write, but
> > not
> > for an error.
> >
> > Fixes: 6a218b9c3183 ("nfs/localio: do not issue misaligned DIO out-
> > of-order")
> > Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
>
> Thanks, definitely cleaner to not have the awkward force_done flag,
> sorry for that nastiness.
>
> But this one needs to be rebased on tip of linus' master due to
> commit
> 3af870aedbff ("nfs/localio: fix regression due to out-of-order
> __put_cred") which landed after the 6.19 merge.
>
> Like so:
>
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
> Date: Sat, 3 Jan 2026 12:14:57 -0500
> Subject: [PATCH] NFS/localio: Stop further I/O upon hitting an error
>
> If the call into the filesystem results in an I/O error, then the
> next
> chunk of data won't be contiguous with the end of the last successful
> chunk. So break out of the I/O loop and report the results.
> Currently the localio code will do this for a short read/write, but
> not
> for an error.
>
> Fixes: 6a218b9c3183 ("nfs/localio: do not issue misaligned DIO out-
> of-order")
> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
> Reviewed-by: Mike Snitzer <snitzer@kernel.org>
> Signed-off-by: Mike Snitzer <snitzer@kernel.org>
> ---
> fs/nfs/localio.c | 30 ++++++++++++++----------------
> 1 file changed, 14 insertions(+), 16 deletions(-)
>
> diff --git a/fs/nfs/localio.c b/fs/nfs/localio.c
> index ed2a7efaf8f20..97e4733d04714 100644
> --- a/fs/nfs/localio.c
> +++ b/fs/nfs/localio.c
> @@ -619,7 +619,6 @@ static void nfs_local_call_read(struct
> work_struct *work)
> container_of(work, struct nfs_local_kiocb, work);
> struct file *filp = iocb->kiocb.ki_filp;
> const struct cred *save_cred;
> - bool force_done = false;
> ssize_t status;
> int n_iters;
>
> @@ -639,13 +638,13 @@ static void nfs_local_call_read(struct
> work_struct *work)
> status = filp->f_op->read_iter(&iocb->kiocb, &iocb-
> >iters[i]);
> revert_creds(save_cred);
>
> - if (status != -EIOCBQUEUED) {
> - if (unlikely(status >= 0 && status < iocb-
> >iters[i].count))
> - force_done = true; /* Partial read
> */
> - if (nfs_local_pgio_done(iocb, status,
> force_done)) {
> - nfs_local_read_iocb_done(iocb);
> - break;
> - }
> + if (status == -EIOCBQUEUED)
> + continue;
> + /* Break on completion, errors, or short reads */
> + if (nfs_local_pgio_done(iocb, status, false) ||
> status < 0 ||
> + (size_t)status < iov_iter_count(&iocb-
> >iters[i])) {
> + nfs_local_read_iocb_done(iocb);
> + break;
> }
> }
> }
> @@ -824,7 +823,6 @@ static void nfs_local_call_write(struct
> work_struct *work)
> struct file *filp = iocb->kiocb.ki_filp;
> unsigned long old_flags = current->flags;
> const struct cred *save_cred;
> - bool force_done = false;
> ssize_t status;
> int n_iters;
>
> @@ -847,13 +845,13 @@ static void nfs_local_call_write(struct
> work_struct *work)
> status = filp->f_op->write_iter(&iocb->kiocb, &iocb-
> >iters[i]);
> revert_creds(save_cred);
>
> - if (status != -EIOCBQUEUED) {
> - if (unlikely(status >= 0 && status < iocb-
> >iters[i].count))
> - force_done = true; /* Partial write
> */
> - if (nfs_local_pgio_done(iocb, status,
> force_done)) {
> - nfs_local_write_iocb_done(iocb);
> - break;
> - }
> + if (status == -EIOCBQUEUED)
> + continue;
> + /* Break on completion, errors, or short writes */
> + if (nfs_local_pgio_done(iocb, status, false) ||
> status < 0 ||
> + (size_t)status < iov_iter_count(&iocb-
> >iters[i])) {
> + nfs_local_write_iocb_done(iocb);
> + break;
> }
> }
> file_end_write(filp);
Yep. I rebased my testing branch yesterday, and caught that.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trondmy@kernel.org, trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2026-01-05 17:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-03 17:14 [PATCH 0/4] Fix misc localio issues Trond Myklebust
2026-01-03 17:14 ` [PATCH 1/4] NFS/localio: Stop further I/O upon hitting an error Trond Myklebust
2026-01-05 17:19 ` Mike Snitzer
2026-01-05 17:35 ` Trond Myklebust [this message]
2026-01-03 17:14 ` [PATCH 2/4] NFS/localio: Deal with page bases that are > PAGE_SIZE Trond Myklebust
2026-01-05 17:40 ` Mike Snitzer
2026-01-03 17:14 ` [PATCH 3/4] NFS/localio: Handle short writes by retrying Trond Myklebust
2026-01-05 18:04 ` Mike Snitzer
2026-01-05 18:09 ` Trond Myklebust
2026-01-05 18:30 ` Mike Snitzer
2026-01-03 17:15 ` [PATCH 4/4] NFS/localio: Cleanup the nfs_local_pgio_done() parameters Trond Myklebust
2026-01-05 17:24 ` Mike Snitzer
2026-01-07 16:08 ` [PATCH 0/4] NFS/localio: various improvements Mike Snitzer
2026-01-07 16:08 ` [PATCH 1/4] NFS/localio: prevent direct reclaim recursion into NFS via nfs_writepages Mike Snitzer
2026-01-07 16:08 ` [PATCH 2/4] NFS/localio: use GFP_NOIO and non-memreclaim workqueue in nfs_local_commit Mike Snitzer
2026-01-07 16:08 ` [PATCH 3/4] NFS/localio: remove -EAGAIN handling in nfs_local_doio() Mike Snitzer
2026-01-07 16:08 ` [PATCH 4/4] NFS/localio: switch nfs_local_do_read and nfs_local_do_write to return void Mike Snitzer
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=09331fd9a94cb5bb8ffa7ae4bcfc3f8f5af06def.camel@kernel.org \
--to=trondmy@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=snitzer@kernel.org \
/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