From: Hanna Czenczek <hreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Hanna Czenczek <hreitz@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Brian Song <hibriansong@gmail.com>
Subject: [PATCH v5 01/25] fuse: Copy write buffer content before polling
Date: Mon, 9 Mar 2026 16:08:32 +0100 [thread overview]
Message-ID: <20260309150856.26800-2-hreitz@redhat.com> (raw)
In-Reply-To: <20260309150856.26800-1-hreitz@redhat.com>
aio_poll() in I/O functions can lead to nested read_from_fuse_export()
calls, overwriting the request buffer's content. The only function
affected by this is fuse_write(), which therefore must use a bounce
buffer or corruption may occur.
Note that in addition we do not know whether libfuse-internal structures
can cope with this nesting, and even if we did, we probably cannot rely
on it in the future. This is the main reason why we want to remove
libfuse from the I/O path.
I do not have a good reproducer for this other than:
$ dd if=/dev/urandom of=image bs=1M count=4096
$ dd if=/dev/zero of=copy bs=1M count=4096
$ touch fuse-export
$ qemu-storage-daemon \
--blockdev file,node-name=file,filename=copy \
--export \
fuse,id=exp,node-name=file,mountpoint=fuse-export,writable=true \
&
Other shell:
$ qemu-img convert -p -n -f raw -O raw -t none image fuse-export
$ killall -SIGINT qemu-storage-daemon
$ qemu-img compare image copy
Content mismatch at offset 0!
(The -t none in qemu-img convert is important.)
I tried reproducing this with throttle and small aio_write requests from
another qemu-io instance, but for some reason all requests are perfectly
serialized then.
I think in theory we should get parallel writes only if we set
fi->parallel_direct_writes in fuse_open(). In fact, I can confirm that
if we do that, that throttle-based reproducer works (i.e. does get
parallel (nested) write requests). I have no idea why we still get
parallel requests with qemu-img convert anyway.
Also, a later patch in this series will set fi->parallel_direct_writes
and note that it makes basically no difference when running fio on the
current libfuse-based version of our code. It does make a difference
without libfuse. So something quite fishy is going on.
I will try to investigate further what the root cause is, but I think
for now let's assume that calling blk_pwrite() can invalidate the buffer
contents through nested polling.
Cc: qemu-stable@nongnu.org
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Hanna Czenczek <hreitz@redhat.com>
---
block/export/fuse.c | 17 ++++++++++++++++-
1 file changed, 16 insertions(+), 1 deletion(-)
diff --git a/block/export/fuse.c b/block/export/fuse.c
index 8cf4572f78..cea9de61f1 100644
--- a/block/export/fuse.c
+++ b/block/export/fuse.c
@@ -301,6 +301,12 @@ static void read_from_fuse_export(void *opaque)
goto out;
}
+ /*
+ * Note that aio_poll() in any request-processing function can lead to a
+ * nested read_from_fuse_export() call, which will overwrite the contents of
+ * exp->fuse_buf. Anything that takes a buffer needs to take care that the
+ * content is copied before potentially polling via aio_poll().
+ */
fuse_session_process_buf(exp->fuse_session, &exp->fuse_buf);
out:
@@ -624,6 +630,7 @@ static void fuse_write(fuse_req_t req, fuse_ino_t inode, const char *buf,
size_t size, off_t offset, struct fuse_file_info *fi)
{
FuseExport *exp = fuse_req_userdata(req);
+ QEMU_AUTO_VFREE void *copied = NULL;
int64_t length;
int ret;
@@ -638,6 +645,14 @@ static void fuse_write(fuse_req_t req, fuse_ino_t inode, const char *buf,
return;
}
+ /*
+ * Heed the note on read_from_fuse_export(): If we call aio_poll() (which
+ * any blk_*() I/O function may do), read_from_fuse_export() may be nested,
+ * overwriting the request buffer content. Therefore, we must copy it here.
+ */
+ copied = blk_blockalign(exp->common.blk, size);
+ memcpy(copied, buf, size);
+
/**
* Clients will expect short writes at EOF, so we have to limit
* offset+size to the image length.
@@ -660,7 +675,7 @@ static void fuse_write(fuse_req_t req, fuse_ino_t inode, const char *buf,
}
}
- ret = blk_pwrite(exp->common.blk, offset, size, buf, 0);
+ ret = blk_pwrite(exp->common.blk, offset, size, copied, 0);
if (ret >= 0) {
fuse_reply_write(req, size);
} else {
--
2.53.0
next prev parent reply other threads:[~2026-03-09 15:11 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 15:08 [PATCH v5 00/25] export/fuse: Use coroutines and multi-threading Hanna Czenczek
2026-03-09 15:08 ` Hanna Czenczek [this message]
2026-03-09 15:08 ` [PATCH v5 02/25] fuse: Ensure init clean-up even with error_fatal Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 03/25] fuse: Remove superfluous empty line Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 04/25] fuse: Explicitly set inode ID to 1 Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 05/25] fuse: Change setup_... to mount_fuse_export() Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 06/25] fuse: Destroy session on mount_fuse_export() fail Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 07/25] fuse: Fix mount options Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 08/25] fuse: Set direct_io and parallel_direct_writes Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 09/25] fuse: Introduce fuse_{at,de}tach_handlers() Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 10/25] fuse: Introduce fuse_{inc,dec}_in_flight() Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 11/25] fuse: Add halted flag Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 12/25] fuse: fuse_{read,write}: Rename length to blk_len Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 13/25] iotests/308: Use conv=notrunc to test growability Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 14/25] fuse: Explicitly handle non-grow post-EOF accesses Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 15/25] block: Move qemu_fcntl_addfl() into osdep.c Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 16/25] fuse: Drop permission changes in fuse_do_truncate Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 17/25] fuse: Manually process requests (without libfuse) Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 18/25] fuse: Reduce max read size Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 19/25] fuse: Process requests in coroutines Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 20/25] block/export: Add multi-threading interface Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 21/25] iotests/307: Test multi-thread export interface Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 22/25] fuse: Make shared export state atomic Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 23/25] fuse: Implement multi-threading Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 24/25] qapi/block-export: Document FUSE's multi-threading Hanna Czenczek
2026-03-09 15:08 ` [PATCH v5 25/25] iotests/308: Add multi-threading sanity test Hanna Czenczek
2026-03-10 11:13 ` [PATCH v5 00/25] export/fuse: Use coroutines and multi-threading Kevin Wolf
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=20260309150856.26800-2-hreitz@redhat.com \
--to=hreitz@redhat.com \
--cc=hibriansong@gmail.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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.