From: info@democraticnet.de
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Joris Gutjahr <joris.gutjahr@protonmail.com>
Subject: [PATCH] Updating the documentation of struct file_system_type
Date: Tue, 1 Dec 2020 22:05:51 +0100 [thread overview]
Message-ID: <20201201210551.8306-1-info@democraticnet.de> (raw)
From: Joris Gutjahr <joris.gutjahr@protonmail.com>
In the documentation of struct file_system_type,
using the definition of the struct of the kernel v5.10-rc6.
Signed-off-by: Joris Gutjahr <joris.gutjahr@protonmail.com>
---
Documentation/filesystems/vfs.rst | 28 +++++++++++++++++++++++-----
1 file changed, 23 insertions(+), 5 deletions(-)
diff --git a/Documentation/filesystems/vfs.rst b/Documentation/filesystems/vfs.rst
index ca52c82e5bb5..364ef3dcb649 100644
--- a/Documentation/filesystems/vfs.rst
+++ b/Documentation/filesystems/vfs.rst
@@ -107,22 +107,30 @@ file /proc/filesystems.
struct file_system_type
-----------------------
-This describes the filesystem. As of kernel 2.6.39, the following
-members are defined:
+This describes the filesystem. As of kernel v5.10, the following
+members are defined: (compare: include/linux/fs.h)
.. code-block:: c
- struct file_system_operations {
+ struct file_system_type {
const char *name;
int fs_flags;
+ int (*init_fs_context)(struct fs_context*);
+ const struct fs_parameter_spec *parameters;
struct dentry *(*mount) (struct file_system_type *, int,
const char *, void *);
void (*kill_sb) (struct super_block *);
struct module *owner;
struct file_system_type * next;
- struct list_head fs_supers;
+ struct hlist_head fs_supers;
struct lock_class_key s_lock_key;
struct lock_class_key s_umount_key;
+ struct lock_class_key s_vfs_rename_key;
+ struct lock_class_key s_writers_key[SB_FREEZE_LEVELS];
+
+ struct lock_class_key i_lock_key;
+ struct lock_class_key i_mutex_key;
+ struct lock_class_key i_mutex_dir_key;
};
``name``
@@ -132,6 +140,12 @@ members are defined:
``fs_flags``
various flags (i.e. FS_REQUIRES_DEV, FS_NO_DCACHE, etc.)
+``init_fs_context``
+ TODO
+
+``fs_parameter_spec``
+ TODO
+
``mount``
the method to call when a new instance of this filesystem should
be mounted
@@ -148,7 +162,11 @@ members are defined:
``next``
for internal VFS use: you should initialize this to NULL
- s_lock_key, s_umount_key: lockdep-specific
+``fs_supers``
+ TODO
+
+
+ s_lock_key, s_umount_key, s_vfs_rename_key, s_writers_key, i_lock_key, i_mutex_key, i_mutex_dir_key: lockdep-specific
The mount() method has the following arguments:
--
2.17.1
next reply other threads:[~2020-12-01 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 21:05 info [this message]
2020-12-03 22:52 ` [PATCH] Updating the documentation of struct file_system_type Jonathan Corbet
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=20201201210551.8306-1-info@democraticnet.de \
--to=info@democraticnet.de \
--cc=corbet@lwn.net \
--cc=joris.gutjahr@protonmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).