Linux network filesystem support library
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Christian Brauner <brauner@kernel.org>,
	Steve French <sfrench@samba.org>,
	Jeff Layton <jlayton@kernel.org>,
	netfs@lists.linux.dev, linux-fsdevel@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfs: Advance iterator correctly rather than jumping it
Date: Fri, 27 Sep 2024 10:11:33 +0200	[thread overview]
Message-ID: <20240927-weinreben-ortstarif-e855de189596@brauner> (raw)
In-Reply-To: <2238548.1727424522@warthog.procyon.org.uk>

On Fri, 27 Sep 2024 09:08:42 +0100, David Howells wrote:
> In netfs_write_folio(), use iov_iter_advance() to advance the folio as we
> split bits of it off to subrequests rather than manually jumping the
> ->iov_offset value around.  This becomes more problematic when we use a
> bounce buffer made out of single-page folios to cover a multipage pagecache
> folio.
> 
> 
> [...]

Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.

Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.

It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.

Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes

[1/1] netfs: Advance iterator correctly rather than jumping it
      https://git.kernel.org/vfs/vfs/c/507a9ef9e851

      reply	other threads:[~2024-09-27  8:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27  8:08 [PATCH] netfs: Advance iterator correctly rather than jumping it David Howells
2024-09-27  8:11 ` Christian Brauner [this message]

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=20240927-weinreben-ortstarif-e855de189596@brauner \
    --to=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=jlayton@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netfs@lists.linux.dev \
    --cc=sfrench@samba.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