From: Amir Goldstein <amir73il@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-unionfs@vger.kernel.org, containers@lists.linux.dev,
linux-fsdevel@vger.kernel.org
Subject: [PATCH v2 2/6] fs: tidy up fs_flags definitions
Date: Mon, 28 Feb 2022 13:39:06 +0200 [thread overview]
Message-ID: <20220228113910.1727819-3-amir73il@gmail.com> (raw)
In-Reply-To: <20220228113910.1727819-1-amir73il@gmail.com>
Use bit shift for flag constants and abbreviate comments.
Signed-off-by: Amir Goldstein <amir73il@gmail.com>
---
include/linux/fs.h | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index e2d892b201b0..f220db331dba 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -2428,13 +2428,13 @@ int sync_inode_metadata(struct inode *inode, int wait);
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_RENAME_DOES_D_MOVE 32768 /* FS will handle d_move() during rename() internally. */
+#define FS_REQUIRES_DEV (1<<0)
+#define FS_BINARY_MOUNTDATA (1<<1)
+#define FS_HAS_SUBTYPE (1<<2)
+#define FS_USERNS_MOUNT (1<<3) /* Can be mounted by userns root */
+#define FS_DISALLOW_NOTIFY_PERM (1<<4) /* Disable fanotify permission events */
+#define FS_ALLOW_IDMAP (1<<5) /* FS can handle vfs idmappings */
+#define FS_RENAME_DOES_D_MOVE (1<<15) /* FS will handle d_move() internally */
int (*init_fs_context)(struct fs_context *);
const struct fs_parameter_spec *parameters;
struct dentry *(*mount) (struct file_system_type *, int,
--
2.25.1
next prev parent reply other threads:[~2022-02-28 11:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 11:39 [PATCH v2 0/6] Generic per-mount io stats Amir Goldstein
2022-02-28 11:39 ` [PATCH v2 1/6] fs: add iostats counters to struct mount Amir Goldstein
2022-02-28 11:39 ` Amir Goldstein [this message]
2022-02-28 11:39 ` [PATCH v2 3/6] fs: collect per-mount io stats Amir Goldstein
2022-02-28 11:39 ` [PATCH v2 4/6] fs: report " Amir Goldstein
2022-02-28 15:06 ` Miklos Szeredi
2022-02-28 16:18 ` Amir Goldstein
2022-02-28 16:31 ` Miklos Szeredi
2022-02-28 17:06 ` Amir Goldstein
2022-02-28 21:11 ` Dave Chinner
2022-02-28 21:57 ` Amir Goldstein
2022-03-01 9:46 ` Dave Chinner
2022-03-01 10:56 ` Amir Goldstein
2022-02-28 11:39 ` [PATCH v2 5/6] ovl: opt-in for " Amir Goldstein
2022-02-28 11:39 ` [PATCH v2 6/6] fuse: " Amir Goldstein
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=20220228113910.1727819-3-amir73il@gmail.com \
--to=amir73il@gmail.com \
--cc=containers@lists.linux.dev \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=viro@zeniv.linux.org.uk \
/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).