Re: [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>, <linux-fscrypt@xxxxxxxxxxxxxxx>, <linux-ext4@xxxxxxxxxxxxxxx>, <linux-f2fs-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
From: Chao Yu <yuchao0@xxxxxxxxxx>
Date: Mon, 19 Nov 2018 14:24:31 +0800
Cc: <ebiggers@xxxxxxxxxx>, <tytso@xxxxxxx>
In-reply-to: <20181119052324.31456-3-chandan@linux.vnet.ibm.com>
References: <20181119052324.31456-1-chandan@linux.vnet.ibm.com> <20181119052324.31456-3-chandan@linux.vnet.ibm.com>
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

On 2018/11/19 13:23, Chandan Rajendra wrote:
> This commit removes the f2fs specific f2fs_encrypted_inode() and makes
> use of the generic IS_ENCRYPTED() macro to check for the encryption
> status of an inode.
> 
> Signed-off-by: Chandan Rajendra <chandan@xxxxxxxxxxxxxxxxxx>

Acked-by: Chao Yu <yuchao0@xxxxxxxxxx>

Thanks,

References:
- [PATCH 0/7] Remove fs specific fscrypt and fsverity build config options
  - From: Chandan Rajendra
- [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
  - From: Chandan Rajendra

Prev by Date: [PATCH 6/7] f2fs: use IS_VERITY() to check inode's fsverity status
Next by Date: Re: [f2fs-dev] [PATCH 6/7] f2fs: use IS_VERITY() to check inode's fsverity status
Previous by thread: [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
Next by thread: Re: [f2fs-dev] [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]

Powered by Linux