From: Russ Fellows <russ.fellows@gmail.com>
To: miklos@szeredi.hu, fuse-devel@lists.linux.dev,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Amir Goldstein <amir73il@gmail.com>,
Russ Fellows <russ.fellows@gmail.com>
Subject: [PATCH v3 2/2] fuse: allow parallel direct writes in passthrough write_iter
Date: Tue, 16 Jun 2026 23:13:22 +0000 [thread overview]
Message-ID: <20260616231325.16788-3-russ.fellows@gmail.com> (raw)
In-Reply-To: <20260616231325.16788-1-russ.fellows@gmail.com>
fuse_passthrough_write_iter() unconditionally called fuse_dio_lock()
from file.c, which required those helpers to be exported. That coupling
is unnecessary and the exported symbols are undesirable.
Replace the fuse_dio_lock()/fuse_dio_unlock() calls with a
passthrough-specific pair, fuse_passthrough_lock() and
fuse_passthrough_unlock(), that is self-contained in passthrough.c.
The new fuse_passthrough_lock() allows shared inode locking only when
all of the following are true:
- the open carries FOPEN_PARALLEL_DIRECT_WRITES
- the write is direct I/O (IOCB_DIRECT)
- the write is not append (IOCB_APPEND absent)
- the write does not extend past EOF
The past-EOF check is made once before the lock is taken (fast path
to choose lock type), and then re-checked after taking the shared lock.
This re-check closes the TOCTOU window: a concurrent writer could extend
EOF between the initial check and the lock acquisition; without the
re-check a shared-lock writer could concurrently update i_size.
Passthrough files are always in uncached iomode (established at open
time via fuse_file_uncached_io_open()), so the fuse_inode_uncached_io_start()
guard from fuse_dio_lock() is not needed here.
Restore fuse_dio_lock() and fuse_dio_unlock() to file-private (static).
Remove their declarations from fuse_i.h.
Signed-off-by: Russ Fellows <russ.fellows@gmail.com>
---
fs/fuse/file.c | 6 ++--
fs/fuse/fuse_i.h | 2 --
fs/fuse/passthrough.c | 74 +++++++++++++++++++++++++++++++++++++++++--
3 files changed, 75 insertions(+), 7 deletions(-)
diff --git a/fs/fuse/file.c b/fs/fuse/file.c
index 7cba331d0..f8651a195 100644
--- a/fs/fuse/file.c
+++ b/fs/fuse/file.c
@@ -1366,8 +1366,8 @@ static bool fuse_dio_wr_exclusive_lock(struct kiocb *iocb, struct iov_iter *from
return false;
}
-void fuse_dio_lock(struct kiocb *iocb, struct iov_iter *from,
- bool *exclusive)
+static void fuse_dio_lock(struct kiocb *iocb, struct iov_iter *from,
+ bool *exclusive)
{
struct inode *inode = file_inode(iocb->ki_filp);
struct fuse_inode *fi = get_fuse_inode(inode);
@@ -1393,7 +1393,7 @@ void fuse_dio_lock(struct kiocb *iocb, struct iov_iter *from,
}
}
-void fuse_dio_unlock(struct kiocb *iocb, bool exclusive)
+static void fuse_dio_unlock(struct kiocb *iocb, bool exclusive)
{
struct inode *inode = file_inode(iocb->ki_filp);
struct fuse_inode *fi = get_fuse_inode(inode);
diff --git a/fs/fuse/fuse_i.h b/fs/fuse/fuse_i.h
index 8d05c7c52..cc428d04b 100644
--- a/fs/fuse/fuse_i.h
+++ b/fs/fuse/fuse_i.h
@@ -1507,8 +1507,6 @@ int fuse_file_io_open(struct file *file, struct inode *inode);
void fuse_file_io_release(struct fuse_file *ff, struct inode *inode);
/* file.c */
-void fuse_dio_lock(struct kiocb *iocb, struct iov_iter *from, bool *exclusive);
-void fuse_dio_unlock(struct kiocb *iocb, bool exclusive);
struct fuse_file *fuse_file_open(struct fuse_mount *fm, u64 nodeid,
unsigned int open_flags, bool isdir);
void fuse_file_release(struct inode *inode, struct fuse_file *ff,
diff --git a/fs/fuse/passthrough.c b/fs/fuse/passthrough.c
index ee822a983..11c16de4d 100644
--- a/fs/fuse/passthrough.c
+++ b/fs/fuse/passthrough.c
@@ -25,6 +25,76 @@ static void fuse_passthrough_end_write(struct kiocb *iocb, ssize_t ret)
fuse_write_update_attr(inode, iocb->ki_pos, ret);
}
+static bool fuse_passthrough_io_past_eof(struct kiocb *iocb,
+ struct iov_iter *iter)
+{
+ struct inode *inode = file_inode(iocb->ki_filp);
+
+ return iocb->ki_pos + iov_iter_count(iter) > i_size_read(inode);
+}
+
+/*
+ * Decide whether an exclusive inode lock is required for a passthrough write
+ * before the lock is taken. Returns true (exclusive needed) unless all of:
+ * - server advertised FOPEN_PARALLEL_DIRECT_WRITES
+ * - write is direct I/O (not buffered)
+ * - write is not append
+ * - write does not appear to extend past EOF (re-checked after lock below)
+ */
+static bool fuse_passthrough_write_needs_exclusive(struct kiocb *iocb,
+ struct iov_iter *iter)
+{
+ struct fuse_file *ff = iocb->ki_filp->private_data;
+
+ if (!(ff->open_flags & FOPEN_PARALLEL_DIRECT_WRITES))
+ return true;
+
+ if (!(iocb->ki_flags & IOCB_DIRECT))
+ return true;
+ if (iocb->ki_flags & IOCB_APPEND)
+ return true;
+ if (fuse_passthrough_io_past_eof(iocb, iter))
+ return true;
+
+ return false;
+}
+
+static void fuse_passthrough_lock(struct kiocb *iocb, struct iov_iter *iter,
+ bool *exclusive)
+{
+ struct inode *inode = file_inode(iocb->ki_filp);
+
+ *exclusive = fuse_passthrough_write_needs_exclusive(iocb, iter);
+ if (*exclusive) {
+ inode_lock(inode);
+ } else {
+ inode_lock_shared(inode);
+ /*
+ * The past-EOF check in fuse_passthrough_write_needs_exclusive()
+ * was made without holding the inode lock and may have raced
+ * with a concurrent EOF-extending write. Re-check under the
+ * shared lock and upgrade to exclusive if the write now reaches
+ * past EOF, to ensure i_size is never updated without exclusive
+ * serialisation.
+ */
+ if (fuse_passthrough_io_past_eof(iocb, iter)) {
+ inode_unlock_shared(inode);
+ inode_lock(inode);
+ *exclusive = true;
+ }
+ }
+}
+
+static void fuse_passthrough_unlock(struct kiocb *iocb, bool exclusive)
+{
+ struct inode *inode = file_inode(iocb->ki_filp);
+
+ if (exclusive)
+ inode_unlock(inode);
+ else
+ inode_unlock_shared(inode);
+}
+
ssize_t fuse_passthrough_read_iter(struct kiocb *iocb, struct iov_iter *iter)
{
struct file *file = iocb->ki_filp;
@@ -70,10 +140,10 @@ ssize_t fuse_passthrough_write_iter(struct kiocb *iocb,
if (!count)
return 0;
- fuse_dio_lock(iocb, iter, &exclusive);
+ fuse_passthrough_lock(iocb, iter, &exclusive);
ret = backing_file_write_iter(backing_file, iter, iocb, iocb->ki_flags,
&ctx);
- fuse_dio_unlock(iocb, exclusive);
+ fuse_passthrough_unlock(iocb, exclusive);
return ret;
}
--
2.51.0
next prev parent reply other threads:[~2026-06-16 23:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 23:13 [PATCH v3 0/2] fuse: fix passthrough parallel direct writes Russ Fellows
2026-06-16 23:13 ` [PATCH v3 1/2] fuse: preserve FOPEN_PARALLEL_DIRECT_WRITES for passthrough opens Russ Fellows
2026-06-19 8:12 ` Amir Goldstein
2026-06-16 23:13 ` Russ Fellows [this message]
2026-06-19 9:05 ` [PATCH v3 2/2] fuse: allow parallel direct writes in passthrough write_iter Amir Goldstein
2026-07-26 1:59 ` [PATCH v4 0/2] fuse: allow parallel direct writes for passthrough Russ Fellows
2026-07-26 1:59 ` [PATCH v4 1/2] fuse: preserve FOPEN_PARALLEL_DIRECT_WRITES for passthrough opens Russ Fellows
2026-07-26 1:59 ` [PATCH v4 2/2] fuse: allow parallel direct writes in passthrough write_iter Russ Fellows
2026-08-01 19:41 ` [PATCH v4 0/2] fuse: allow parallel direct writes for passthrough Amir Goldstein
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=20260616231325.16788-3-russ.fellows@gmail.com \
--to=russ.fellows@gmail.com \
--cc=amir73il@gmail.com \
--cc=fuse-devel@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®