From: Jiachen Zhang <zhangjiachen.jaycee@bytedance.com>
To: Miklos Szeredi <miklos@szeredi.hu>,
Jonathan Corbet <corbet@lwn.net>,
linux-fsdevel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: me@jcix.top, Jiachen Zhang <zhangjiachen.jaycee@bytedance.com>
Subject: [PATCH 0/5] FUSE consistency improvements
Date: Tue, 11 Jul 2023 12:34:00 +0800 [thread overview]
Message-ID: <20230711043405.66256-1-zhangjiachen.jaycee@bytedance.com> (raw)
This patchset resends some patches that related to FUSE consistency
improvements in the mailing list.
The 1st patch fixes a staleness-checking issue, which is the v2 version
of the patch[1].
The 2nd patch is a resend version of the patch[2] with its commit message
rewritten.
The 3rd and 4th patches are new versions of the patch[3] and the patch[4],
FUSE filesystems are able to implement the close-to-open (CTO) consistency
semantics with the help of these two patches. The 5th patch is a new
patch which improves the explanation of FUSE cache mode and consistency
models in the documentation.
[1] [PATCH] fuse: initialize attr_version of new fuse inodes by fc->attr_version,
https://lore.kernel.org/lkml/20221111093702.80975-1-zhangjiachen.jaycee@bytedance.com/
[2] [PATCH] fuse: invalidate dentry on EEXIST creates or ENOENT deletes,
https://lore.kernel.org/lkml/20220805131823.83544-1-zhangjiachen.jaycee@bytedance.com/
[3] [PATCH] fuse: add FOPEN_INVAL_ATTR,
https://lore.kernel.org/lkml/20220608104202.19461-1-zhangjiachen.jaycee@bytedance.com/
[4] [PATCH] fuse: writeback_cache consistency enhancement (writeback_cache_v2),
https://lore.kernel.org/lkml/20220624055825.29183-1-zhangjiachen.jaycee@bytedance.com/
Jiachen Zhang (5):
fuse: check attributes staleness on fuse_iget()
fuse: invalidate dentry on EEXIST creates or ENOENT deletes
fuse: add FOPEN_INVAL_ATTR
fuse: writeback_cache consistency enhancement (writeback_cache_v2)
docs: fuse: improve FUSE consistency explanation
Documentation/filesystems/fuse-io.rst | 32 +++++++++++++++--
fs/fuse/dir.c | 11 +++---
fs/fuse/file.c | 35 +++++++++++++++++++
fs/fuse/fuse_i.h | 6 ++++
fs/fuse/inode.c | 49 +++++++++++++++++++++++++--
include/uapi/linux/fuse.h | 11 +++++-
6 files changed, 135 insertions(+), 9 deletions(-)
--
2.20.1
next reply other threads:[~2023-07-11 4:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 4:34 Jiachen Zhang [this message]
2023-07-11 4:34 ` [PATCH 1/5] fuse: check attributes staleness on fuse_iget() Jiachen Zhang
2023-08-23 8:57 ` Miklos Szeredi
2023-07-11 4:34 ` [PATCH 2/5] fuse: invalidate dentry on EEXIST creates or ENOENT deletes Jiachen Zhang
2023-08-16 12:27 ` Miklos Szeredi
2023-07-11 4:34 ` [PATCH 3/5] fuse: add FOPEN_INVAL_ATTR Jiachen Zhang
2023-08-23 9:01 ` Miklos Szeredi
2023-08-23 11:12 ` Jiachen Zhang
2023-07-11 4:34 ` [PATCH 4/5] fuse: writeback_cache consistency enhancement (writeback_cache_v2) Jiachen Zhang
2023-08-23 9:07 ` Miklos Szeredi
2023-08-23 10:35 ` Bernd Schubert
2023-08-23 10:59 ` Jiachen Zhang
2023-08-23 22:55 ` Bernd Schubert
2023-07-11 4:34 ` [PATCH 5/5] docs: fuse: improve FUSE consistency explanation Jiachen Zhang
2023-07-11 4:42 ` Randy Dunlap
2023-07-11 7:15 ` Jiachen Zhang
2023-07-14 5:50 ` [PATCH 0/5] FUSE consistency improvements Jingbo Xu
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=20230711043405.66256-1-zhangjiachen.jaycee@bytedance.com \
--to=zhangjiachen.jaycee@bytedance.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@jcix.top \
--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).