From: I Hsin Cheng <richard120310@gmail.com>
To: corbet@lwn.net
Cc: willy@infradead.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
skhan@linuxfoundation.org, linux-kernel-mentees@lists.linux.dev,
I Hsin Cheng <richard120310@gmail.com>
Subject: [PATCH] docs: vfs: Update struct file_system_type
Date: Sun, 23 Mar 2025 11:47:25 +0800 [thread overview]
Message-ID: <20250323034725.32329-1-richard120310@gmail.com> (raw)
The structure definition now in the kernel adds macros defining the
value of "fs_flags", and the value "FS_NO_DCACHE" no longer exists,
update it to an existing flag value.
Signed-off-by: I Hsin Cheng <richard120310@gmail.com>
---
Documentation/filesystems/vfs.rst | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/Documentation/filesystems/vfs.rst b/Documentation/filesystems/vfs.rst
index 31eea688609a..4e7fa09ffb6d 100644
--- a/Documentation/filesystems/vfs.rst
+++ b/Documentation/filesystems/vfs.rst
@@ -115,6 +115,14 @@ members are defined:
struct file_system_type {
const char *name;
int fs_flags;
+ #define FS_REQUIRES_DEV 1
+ #define FS_BINARY_MOUNTDATA 2
+ #define FS_HAS_SUBTYPE 4
+ #define FS_USERNS_MOUNT 8 /* Can be mounted by userns root */
+ #define FS_DISALLOW_NOTIFY_PERM 16 /* Disable fanotify permission events */
+ #define FS_ALLOW_IDMAP 32 /* FS has been updated to handle vfs idmappings. */
+ #define FS_MGTIME 64 /* FS uses multigrain timestamps */
+ #define FS_RENAME_DOES_D_MOVE 32768 /* FS will handle d_move() during rename() internally. */
int (*init_fs_context)(struct fs_context *);
const struct fs_parameter_spec *parameters;
struct dentry *(*mount) (struct file_system_type *, int,
@@ -140,7 +148,7 @@ members are defined:
"msdos" and so on
``fs_flags``
- various flags (i.e. FS_REQUIRES_DEV, FS_NO_DCACHE, etc.)
+ various flags (i.e. FS_REQUIRES_DEV, FS_BINARY_MOUNTDATA, etc.)
``init_fs_context``
Initializes 'struct fs_context' ->ops and ->fs_private fields with
--
2.43.0
next reply other threads:[~2025-03-23 3:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 3:47 I Hsin Cheng [this message]
2025-03-23 14:24 ` [PATCH] docs: vfs: Update struct file_system_type Matthew Wilcox
2025-03-27 14:29 ` I Hsin Cheng
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=20250323034725.32329-1-richard120310@gmail.com \
--to=richard120310@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox