From: Matthew Wilcox <willy@infradead.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Why doesn't FUSE use stable writes?
Date: Sat, 16 Dec 2023 01:05:58 +0000 [thread overview]
Message-ID: <ZXz39r4SR39DmPcW@casper.infradead.org> (raw)
I'm looking at fuse_writepage_locked() and it allocates a new page, then
copies from the page cache into that page before sending that page to
userspace. I imagine you want to prevent torn writes, so why not set
SB_I_STABLE_WRITES instead of having this memcpy?
next reply other threads:[~2023-12-16 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-16 1:05 Matthew Wilcox [this message]
2023-12-16 9:33 ` Why doesn't FUSE use stable writes? 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=ZXz39r4SR39DmPcW@casper.infradead.org \
--to=willy@infradead.org \
--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).