From: David Howells <dhowells@redhat.com>
To: linux-cachefs@redhat.com, linux-afs@lists.infradead.org
Cc: Andrew W Elble <aweits@rit.edu>,
ceph-devel@vger.kernel.org, Matthew Wilcox <willy@infradead.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Jeff Layton <jlayton@kernel.org>,
dhowells@redhat.com, Jeff Layton <jlayton@kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/2] netfs, afs: Fix write_begin/end
Date: Mon, 21 Jun 2021 16:40:06 +0100 [thread overview]
Message-ID: <162429000639.2770648.6368710175435880749.stgit@warthog.procyon.org.uk> (raw)
Here are some patches to fix netfs_write_begin() and afs_write_end() in the
following ways:
(1) In netfs_write_begin(), extract the decision about whether to skip a
page out to its own helper and have that clear around the region to be
written, but not clear that region. This requires the filesystem to
patch it up afterwards if the hole doesn't get completely filled.
(2) Use offset_in_thp() in (1) rather than manually calculating the offset
into the page.
(3) Due to (1), afs_write_end() now needs to handle short data write into
the page by generic_perform_write(). I've adopted an analogous
approach to ceph of just returning 0 in this case and letting the
caller go round again.
Also add a note that (in the future) the len parameter may extend beyond
the page allocated. This is because the page allocation is deferred to
write_begin() and that gets to decide what size of THP to allocate.
The patches can be found here:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=afs-fixes
David
Link: https://lore.kernel.org/r/20210613233345.113565-1-jlayton@kernel.org/
Link: https://lore.kernel.org/r/162367681795.460125.11729955608839747375.stgit@warthog.procyon.org.uk/
Link: https://lore.kernel.org/r/162391823192.1173366.9740514875196345746.stgit@warthog.procyon.org.uk/ # v3
Changes
=======
ver #3:
- Drop the bits that make afs take account of len exceeding the end of
the page in afs_write_begin/end().
ver #2:
- Removed a var that's no longer used (spotted by the kernel test robot)
- Removed a forgotten "noinline".
ver #1:
- Prefixed the Jeff's new helper with "netfs_".
- Don't call zero_user_segments() for a full-page write.
- Altered the beyond-last-page check to avoid a DIV.
- Removed redundant zero-length-file check.
- Added patches to fix afs.
---
David Howells (1):
afs: Fix afs_write_end() to handle short writes
Jeff Layton (1):
netfs: fix test for whether we can skip read when writing beyond EOF
fs/netfs/read_helper.c | 49 +++++++++++++++++++++++++++++++-----------
1 file changed, 36 insertions(+), 13 deletions(-)
next reply other threads:[~2021-06-21 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 15:40 David Howells [this message]
2021-06-21 15:40 ` [PATCH v3 1/2] afs: Fix afs_write_end() to handle short writes David Howells
2021-06-21 16:01 ` Matthew Wilcox
2021-06-21 15:40 ` [PATCH v3 2/2] netfs: fix test for whether we can skip read when writing beyond EOF David Howells
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=162429000639.2770648.6368710175435880749.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=aweits@rit.edu \
--cc=ceph-devel@vger.kernel.org \
--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 \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.