From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, <chao@kernel.org>
Subject: Re: [PATCH] f2fs: fix to show encrypt flag in FS_IOC_GETFLAGS
Date: Tue, 3 Apr 2018 15:14:40 +0800 [thread overview]
Message-ID: <3f76800a-8b68-b378-8b03-c14248966be4@huawei.com> (raw)
In-Reply-To: <20180402202105.GB19195@jaegeuk-macbookpro.roam.corp.google.com>
On 2018/4/3 4:21, Jaegeuk Kim wrote:
> On 04/02, Chao Yu wrote:
>> This patch fixes to show encrypt flag in FS_IOC_GETFLAGS like ext4 does.
>
> Actually, we have to show internal flags owned by f2fs, not generic ones.
> We may need to define all of them separately?
Agreed, I wrote a patch, could check that? and in that patch, do we need to
delete flag definition f2fs don't use?
Thanks,
>
>>
>> Signed-off-by: Chao Yu <yuchao0@huawei.com>
>> ---
>> fs/f2fs/file.c | 9 +++++++--
>> 1 file changed, 7 insertions(+), 2 deletions(-)
>>
>> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
>> index 8068b015ece5..271fadadaa36 100644
>> --- a/fs/f2fs/file.c
>> +++ b/fs/f2fs/file.c
>> @@ -1584,8 +1584,13 @@ static int f2fs_ioc_getflags(struct file *filp, unsigned long arg)
>> {
>> struct inode *inode = file_inode(filp);
>> struct f2fs_inode_info *fi = F2FS_I(inode);
>> - unsigned int flags = fi->i_flags &
>> - (FS_FL_USER_VISIBLE | FS_PROJINHERIT_FL);
>> + unsigned int flags = fi->i_flags;
>> +
>> + if (file_is_encrypt(inode))
>> + flags |= FS_ENCRYPT_FL;
>> +
>> + flags &= FS_FL_USER_VISIBLE | FS_PROJINHERIT_FL;
>> +
>> return put_user(flags, (int __user *)arg);
>> }
>>
>> --
>> 2.15.0.55.gc2ece9dc4de6
>
> .
>
next prev parent reply other threads:[~2018-04-03 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 10:24 Chao Yu
2018-04-02 20:21 ` Jaegeuk Kim
2018-04-03 7:14 ` Chao Yu [this message]
2018-04-05 3:46 ` Jaegeuk Kim
2018-04-08 1:15 ` Chao Yu
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=3f76800a-8b68-b378-8b03-c14248966be4@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®