[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1926821.WNcHRD5IIQ@dhcp-9-109-212-164>
Date: Mon, 06 May 2019 14:31:58 +0530
From: Chandan Rajendra <chandan@...ux.ibm.com>
To: Eric Biggers <ebiggers@...nel.org>
Cc: linux-fscrypt@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
linux-mtd@...ts.infradead.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 08/13] fscrypt: introduce fscrypt_decrypt_block_inplace()
On Thursday, May 2, 2019 4:15:10 AM IST Eric Biggers wrote:
> From: Eric Biggers <ebiggers@...gle.com>
>
> fscrypt_decrypt_page() behaves very differently depending on whether the
> filesystem set FS_CFLG_OWN_PAGES in its fscrypt_operations. This makes
> the function difficult to understand and document. It also makes it so
> that all callers have to provide inode and lblk_num, when fscrypt could
> determine these itself for pagecache pages.
>
> Therefore, move the FS_CFLG_OWN_PAGES behavior into a new function
> fscrypt_decrypt_block_inplace().
>
Looks good to me,
Reviewed-by: Chandan Rajendra <chandan@...ux.ibm.com>
--
chandan
Powered by blists - more mailing lists