From: Matthew Wilcox <willy@infradead.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-cachefs@redhat.com, linux-afs@lists.infradead.org,
Jeff Layton <jlayton@kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] afs: Fix afs_write_end() to handle short writes
Date: Mon, 21 Jun 2021 15:36:53 +0100 [thread overview]
Message-ID: <YNCkBXCo1hiQ0vFs@casper.infradead.org> (raw)
In-Reply-To: <162391825688.1173366.3437507255136307904.stgit@warthog.procyon.org.uk>
On Thu, Jun 17, 2021 at 09:24:16AM +0100, David Howells wrote:
> Fix afs_write_end() to correctly handle a short copy into the intended
> write region of the page. Two things are necessary:
>
> (1) If the page is not up to date, then we should just return 0
> (ie. indicating a zero-length copy). The loop in
> generic_perform_write() will go around again, possibly breaking up the
> iterator into discrete chunks.
>
> This is analogous to commit b9de313cf05fe08fa59efaf19756ec5283af672a
> for ceph.
>
> (2) The page should not have been set uptodate if it wasn't completely set
> up by netfs_write_begin() (this will be fixed in the next patch), so
> we need to set uptodate here in such a case.
>
> Also remove the assertion that was checking that the page was set uptodate
> since it's now set uptodate if it wasn't already a few lines above. The
> assertion was from when uptodate was set elsewhere.
Thanks for adding that explanation.
> +++ b/fs/afs/write.c
> @@ -119,6 +119,16 @@ int afs_write_end(struct file *file, struct address_space *mapping,
> _enter("{%llx:%llu},{%lx}",
> vnode->fid.vid, vnode->fid.vnode, page->index);
>
> + len = min_t(size_t, len, thp_size(page) - from);
This line isn't necessary yet, right?
> + if (!PageUptodate(page)) {
> + if (copied < len) {
> + copied = 0;
> + goto out;
> + }
> +
> + SetPageUptodate(page);
> + }
> +
> if (copied == 0)
> goto out;
>
> @@ -133,8 +143,6 @@ int afs_write_end(struct file *file, struct address_space *mapping,
> write_sequnlock(&vnode->cb_lock);
> }
>
> - ASSERT(PageUptodate(page));
> -
> if (PagePrivate(page)) {
> priv = page_private(page);
> f = afs_page_dirty_from(page, priv);
The rest of this looks good.
next prev parent reply other threads:[~2021-06-21 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 8:23 [PATCH v2 0/3] netfs, afs: Fix netfs_write_begin and THP handling David Howells
2021-06-17 8:24 ` [PATCH v2 1/3] afs: Handle len being extending over page end in write_begin/write_end David Howells
2021-06-21 14:32 ` Matthew Wilcox
2021-06-17 8:24 ` [PATCH v2 2/3] afs: Fix afs_write_end() to handle short writes David Howells
2021-06-21 14:36 ` Matthew Wilcox [this message]
2021-06-17 8:24 ` [PATCH v2 3/3] netfs: fix test for whether we can skip read when writing beyond EOF David Howells
2021-06-21 14:50 ` Matthew Wilcox
2021-06-18 3:46 ` [PATCH v2 0/3] netfs, afs: Fix netfs_write_begin and THP handling Al Viro
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=YNCkBXCo1hiQ0vFs@casper.infradead.org \
--to=willy@infradead.org \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).