From: Wang Shilong <wangshilong1991@gmail.com>
To: linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Cc: Andreas Dilger <adilger@dilger.ca>, Wang Shilong <wshilong@ddn.com>
Subject: [PATCH 2/2] f2fs: only set project inherit bit for directory
Date: Thu, 6 Jun 2019 13:32:25 +0900 [thread overview]
Message-ID: <1559795545-17290-2-git-send-email-wshilong1991@gmail.com> (raw)
In-Reply-To: <1559795545-17290-1-git-send-email-wshilong1991@gmail.com>
From: Wang Shilong <wshilong@ddn.com>
It doesn't make any sense to have project inherit bits
for regular files, even though this won't cause any
problem, but it is better fix this.
Cc: Andreas Dilger <adilger@dilger.ca>
Signed-off-by: Wang Shilong <wshilong@ddn.com>
---
fs/f2fs/f2fs.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
index 06b89a9862ab..f02ebecb68ea 100644
--- a/fs/f2fs/f2fs.h
+++ b/fs/f2fs/f2fs.h
@@ -2370,7 +2370,8 @@ static inline void f2fs_change_bit(unsigned int nr, char *addr)
F2FS_PROJINHERIT_FL)
/* Flags that are appropriate for regular files (all but dir-specific ones). */
-#define F2FS_REG_FLMASK (~(F2FS_DIRSYNC_FL | F2FS_TOPDIR_FL))
+#define F2FS_REG_FLMASK (~(F2FS_DIRSYNC_FL | F2FS_TOPDIR_FL |\
+ F2FS_PROJINHERIT_FL))
/* Flags that are appropriate for non-directories/regular files. */
#define F2FS_OTHER_FLMASK (F2FS_NODUMP_FL | F2FS_NOATIME_FL)
--
2.21.0
next prev parent reply other threads:[~2019-06-06 4:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 4:32 [PATCH 1/2] ext4: only set project inherit bit for directory Wang Shilong
2019-06-06 4:32 ` Wang Shilong [this message]
2019-06-13 6:36 ` [PATCH 2/2] f2fs: " Chao Yu
2019-06-13 6:36 ` [f2fs-dev] " Chao Yu
2019-06-13 7:34 ` 回复: " Wang Shilong via Linux-f2fs-devel
2019-06-13 7:34 ` [f2fs-dev] " Wang Shilong via Linux-f2fs-devel
2019-06-13 8:03 ` Chao Yu
2019-06-13 8:03 ` [f2fs-dev] " Chao Yu
2019-06-06 15:30 ` [PATCH 1/2] ext4: " Darrick J. Wong
2019-06-06 15:30 ` [f2fs-dev] " Darrick J. Wong
2019-06-06 22:45 ` Eric Biggers
2019-06-06 22:45 ` [f2fs-dev] " Eric Biggers
2019-06-07 7:51 ` 回复: " Wang Shilong via Linux-f2fs-devel
2019-06-07 7:51 ` [f2fs-dev] " Wang Shilong via Linux-f2fs-devel
2019-06-07 18:14 ` Eric Biggers
2019-06-07 18:14 ` [f2fs-dev] " Eric Biggers
2019-06-08 1:15 ` 回复: " Wang Shilong via Linux-f2fs-devel
2019-06-08 1:15 ` [f2fs-dev] " Wang Shilong via Linux-f2fs-devel
2019-06-10 4:38 ` Theodore Ts'o
2019-06-10 4:38 ` [f2fs-dev] " Theodore Ts'o
2019-06-10 4:15 ` Theodore Ts'o
2019-06-10 4:15 ` [f2fs-dev] " Theodore Ts'o
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=1559795545-17290-2-git-send-email-wshilong1991@gmail.com \
--to=wangshilong1991@gmail.com \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=wshilong@ddn.com \
/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).