From: Joanne Koong <joannelkoong@gmail.com>
To: miklos@szeredi.hu, linux-fsdevel@vger.kernel.org
Cc: josef@toxicpanda.com, bernd.schubert@fastmail.fm,
jefflexu@linux.alibaba.com, kernel-team@meta.com
Subject: [PATCH v2 5/9] fuse: move initialization of fuse_file to fuse_writepages() instead of in callback
Date: Wed, 21 Aug 2024 16:22:37 -0700 [thread overview]
Message-ID: <20240821232241.3573997-6-joannelkoong@gmail.com> (raw)
In-Reply-To: <20240821232241.3573997-1-joannelkoong@gmail.com>
Prior to this change, data->ff is checked and if not initialized then
initialized in the fuse_writepages_fill() callback, which gets called
for every dirty page in the address space mapping.
This logic is better placed in the main fuse_writepages() caller where
data.ff is initialized before walking the dirty pages.
No functional changes added.
Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
---
fs/fuse/file.c | 20 +++++++++-----------
1 file changed, 9 insertions(+), 11 deletions(-)
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index 8a9b6e8dbd1b..147645d7e5d9 100644
--- a/fs/fuse/file.c
+++ b/fs/fuse/file.c
@@ -2263,13 +2263,6 @@ static int fuse_writepages_fill(struct folio *folio,
struct page *tmp_page;
int err;
- if (!data->ff) {
- err = -EIO;
- data->ff = fuse_write_file_get(fi);
- if (!data->ff)
- goto out_unlock;
- }
-
if (wpa && fuse_writepage_need_send(fc, &folio->page, ap, data)) {
fuse_writepages_send(data);
data->wpa = NULL;
@@ -2348,6 +2341,7 @@ static int fuse_writepages(struct address_space *mapping,
struct writeback_control *wbc)
{
struct inode *inode = mapping->host;
+ struct fuse_inode *fi = get_fuse_inode(inode);
struct fuse_conn *fc = get_fuse_conn(inode);
struct fuse_fill_wb_data data;
int err;
@@ -2361,21 +2355,25 @@ static int fuse_writepages(struct address_space *mapping,
data.inode = inode;
data.wpa = NULL;
- data.ff = NULL;
+ data.ff = fuse_write_file_get(fi);
+ if (!data.ff)
+ return -EIO;
data.orig_pages = kcalloc(fc->max_pages,
sizeof(struct page *),
GFP_NOFS);
- if (!data.orig_pages)
+ if (!data.orig_pages) {
+ fuse_file_put(data.ff, false);
return -ENOMEM;
+ }
err = write_cache_pages(mapping, wbc, fuse_writepages_fill, &data);
if (data.wpa) {
WARN_ON(!data.wpa->ia.ap.num_pages);
fuse_writepages_send(&data);
}
- if (data.ff)
- fuse_file_put(data.ff, false);
+
+ fuse_file_put(data.ff, false);
kfree(data.orig_pages);
return err;
--
2.43.5
next prev parent reply other threads:[~2024-08-21 23:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 23:22 [PATCH v2 0/9] fuse: writeback clean up / refactoring Joanne Koong
2024-08-21 23:22 ` [PATCH v2 1/9] fuse: drop unused fuse_mount arg in fuse_writepage_finish() Joanne Koong
2024-08-21 23:22 ` [PATCH v2 2/9] fuse: refactor finished writeback stats updates into helper function Joanne Koong
2024-08-21 23:22 ` [PATCH v2 3/9] fuse: update stats for pages in dropped aux writeback list Joanne Koong
2024-08-21 23:22 ` [PATCH v2 4/9] fuse: clean up error handling in fuse_writepages() Joanne Koong
2024-08-21 23:22 ` Joanne Koong [this message]
2024-08-22 9:39 ` [PATCH v2 5/9] fuse: move initialization of fuse_file to fuse_writepages() instead of in callback Miklos Szeredi
2024-08-21 23:22 ` [PATCH v2 6/9] fuse: convert fuse_writepages_fill() to use a folio for its tmp page Joanne Koong
2024-08-21 23:22 ` [PATCH v2 7/9] fuse: move folio_start_writeback to after the allocations in fuse_writepage_locked() Joanne Koong
2024-08-21 23:22 ` [PATCH v2 8/9] fuse: refactor out shared logic in fuse_writepages_fill() and fuse_writepage_locked() Joanne Koong
2024-08-22 9:58 ` Miklos Szeredi
2024-08-22 17:08 ` Joanne Koong
2024-08-21 23:22 ` [PATCH v2 9/9] fuse: tidy up error paths " Joanne Koong
2024-08-22 9:59 ` Miklos Szeredi
2024-08-22 9:03 ` [PATCH v2 0/9] fuse: writeback clean up / refactoring Miklos Szeredi
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=20240821232241.3573997-6-joannelkoong@gmail.com \
--to=joannelkoong@gmail.com \
--cc=bernd.schubert@fastmail.fm \
--cc=jefflexu@linux.alibaba.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).