From: Eric Biggers <ebiggers@kernel.org>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Andreas Dilger <adilger@dilger.ca>,
Wang Shilong <wshilong@ddn.com>
Subject: Re: [f2fs-dev] [PATCH 1/2] ext4: only set project inherit bit for directory
Date: Thu, 6 Jun 2019 15:45:25 -0700 [thread overview]
Message-ID: <20190606224525.GB84833@gmail.com> (raw)
In-Reply-To: <1559795545-17290-1-git-send-email-wshilong1991@gmail.com>
On Thu, Jun 06, 2019 at 01:32:24PM +0900, Wang Shilong wrote:
> 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/ext4/ext4.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index 1cb67859e051..ceb74093e138 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -421,7 +421,8 @@ struct flex_groups {
> EXT4_PROJINHERIT_FL | EXT4_CASEFOLD_FL)
>
> /* Flags that are appropriate for regular files (all but dir-specific ones). */
> -#define EXT4_REG_FLMASK (~(EXT4_DIRSYNC_FL | EXT4_TOPDIR_FL | EXT4_CASEFOLD_FL))
> +#define EXT4_REG_FLMASK (~(EXT4_DIRSYNC_FL | EXT4_TOPDIR_FL | EXT4_CASEFOLD_FL |\
> + EXT4_PROJINHERIT_FL))
>
> /* Flags that are appropriate for non-directories/regular files. */
> #define EXT4_OTHER_FLMASK (EXT4_NODUMP_FL | EXT4_NOATIME_FL)
> --
> 2.21.0
Won't this break 'chattr' on files that already have this flag set?
FS_IOC_GETFLAGS will return this flag, so 'chattr' will pass it back to
FS_IOC_SETFLAGS which will return EOPNOTSUPP due to this:
if (ext4_mask_flags(inode->i_mode, flags) != flags)
return -EOPNOTSUPP;
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
linux-ext4@vger.kernel.org, Wang Shilong <wshilong@ddn.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/2] ext4: only set project inherit bit for directory
Date: Thu, 6 Jun 2019 15:45:25 -0700 [thread overview]
Message-ID: <20190606224525.GB84833@gmail.com> (raw)
In-Reply-To: <1559795545-17290-1-git-send-email-wshilong1991@gmail.com>
On Thu, Jun 06, 2019 at 01:32:24PM +0900, Wang Shilong wrote:
> 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/ext4/ext4.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index 1cb67859e051..ceb74093e138 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -421,7 +421,8 @@ struct flex_groups {
> EXT4_PROJINHERIT_FL | EXT4_CASEFOLD_FL)
>
> /* Flags that are appropriate for regular files (all but dir-specific ones). */
> -#define EXT4_REG_FLMASK (~(EXT4_DIRSYNC_FL | EXT4_TOPDIR_FL | EXT4_CASEFOLD_FL))
> +#define EXT4_REG_FLMASK (~(EXT4_DIRSYNC_FL | EXT4_TOPDIR_FL | EXT4_CASEFOLD_FL |\
> + EXT4_PROJINHERIT_FL))
>
> /* Flags that are appropriate for non-directories/regular files. */
> #define EXT4_OTHER_FLMASK (EXT4_NODUMP_FL | EXT4_NOATIME_FL)
> --
> 2.21.0
Won't this break 'chattr' on files that already have this flag set?
FS_IOC_GETFLAGS will return this flag, so 'chattr' will pass it back to
FS_IOC_SETFLAGS which will return EOPNOTSUPP due to this:
if (ext4_mask_flags(inode->i_mode, flags) != flags)
return -EOPNOTSUPP;
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers <ebiggers@kernel.org>
To: Wang Shilong <wangshilong1991@gmail.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
linux-ext4@vger.kernel.org, Wang Shilong <wshilong@ddn.com>,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] ext4: only set project inherit bit for directory
Date: Thu, 6 Jun 2019 15:45:25 -0700 [thread overview]
Message-ID: <20190606224525.GB84833@gmail.com> (raw)
Message-ID: <20190606224525.Qod5eO5BCg4HVWA4XU7GeBIL2bDXKHisxZv1NlskFQs@z> (raw)
In-Reply-To: <1559795545-17290-1-git-send-email-wshilong1991@gmail.com>
On Thu, Jun 06, 2019 at 01:32:24PM +0900, Wang Shilong wrote:
> 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/ext4/ext4.h | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> index 1cb67859e051..ceb74093e138 100644
> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -421,7 +421,8 @@ struct flex_groups {
> EXT4_PROJINHERIT_FL | EXT4_CASEFOLD_FL)
>
> /* Flags that are appropriate for regular files (all but dir-specific ones). */
> -#define EXT4_REG_FLMASK (~(EXT4_DIRSYNC_FL | EXT4_TOPDIR_FL | EXT4_CASEFOLD_FL))
> +#define EXT4_REG_FLMASK (~(EXT4_DIRSYNC_FL | EXT4_TOPDIR_FL | EXT4_CASEFOLD_FL |\
> + EXT4_PROJINHERIT_FL))
>
> /* Flags that are appropriate for non-directories/regular files. */
> #define EXT4_OTHER_FLMASK (EXT4_NODUMP_FL | EXT4_NOATIME_FL)
> --
> 2.21.0
Won't this break 'chattr' on files that already have this flag set?
FS_IOC_GETFLAGS will return this flag, so 'chattr' will pass it back to
FS_IOC_SETFLAGS which will return EOPNOTSUPP due to this:
if (ext4_mask_flags(inode->i_mode, flags) != flags)
return -EOPNOTSUPP;
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2019-06-06 22:45 UTC|newest]
Thread overview: 34+ 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
2019-06-06 4:32 ` [PATCH 2/2] f2fs: " Wang Shilong
2019-06-06 4:32 ` Wang Shilong
2019-06-13 6:36 ` Chao Yu
2019-06-13 6:36 ` [f2fs-dev] " Chao Yu
2019-06-13 6:36 ` Chao Yu
2019-06-13 7:34 ` 回复: " Wang Shilong
2019-06-13 7:34 ` [f2fs-dev] " Wang Shilong via Linux-f2fs-devel
2019-06-13 7:34 ` 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 15:30 ` Darrick J. Wong
2019-06-06 20:50 ` Andreas Dilger
2019-06-06 22:45 ` Eric Biggers [this message]
2019-06-06 22:45 ` [f2fs-dev] " Eric Biggers
2019-06-06 22:45 ` Eric Biggers
2019-06-07 7:51 ` 回复: [f2fs-dev] " Wang Shilong
2019-06-07 7:51 ` [f2fs-dev] 回复: " Wang Shilong via Linux-f2fs-devel
2019-06-07 7:51 ` Wang Shilong via Linux-f2fs-devel
2019-06-07 18:14 ` 回复: [f2fs-dev] " Eric Biggers
2019-06-07 18:14 ` [f2fs-dev] 回复: " Eric Biggers
2019-06-07 18:14 ` Eric Biggers
2019-06-08 1:15 ` 回复: 回复: [f2fs-dev] " Wang Shilong
2019-06-08 1:15 ` [f2fs-dev] 回复: 回复: " Wang Shilong via Linux-f2fs-devel
2019-06-08 1:15 ` Wang Shilong via Linux-f2fs-devel
2019-06-10 4:38 ` 回复: [f2fs-dev] " Theodore Ts'o
2019-06-10 4:38 ` [f2fs-dev] 回复: " Theodore Ts'o
2019-06-10 4:38 ` Theodore Ts'o
2019-06-10 4:15 ` Theodore Ts'o
2019-06-10 4:15 ` [f2fs-dev] " Theodore Ts'o
2019-06-10 4:15 ` 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=20190606224525.GB84833@gmail.com \
--to=ebiggers@kernel.org \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=wangshilong1991@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.