[PATCH 2/6] f2fs: Update outdated comment in f2fs_write_begin()
Eric Biggers <[email protected]>
| Newsgroups | org.kernel.vger.linux-ext4,net.sourceforge.lists.linux-f2fs-devel,org.kernel.vger.linux-block,org.kernel.vger.linux-doc,org.kernel.vger.linux-fscrypt,org.kernel.vger.linux-fsdevel |
|---|---|
| Message-ID | <[email protected]> |
Refer to f2fs_set_bio_crypt_ctx() instead of the removed function f2fs_encrypt_one_page(). Signed-off-by: Eric Biggers <[email protected]> --- fs/f2fs/data.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c index 65117dd2e123..a88ed125d266 100644 --- a/fs/f2fs/data.c +++ b/fs/f2fs/data.c @@ -3956,7 +3956,7 @@ static int f2fs_write_begin(const struct kiocb *iocb, /* * Although the block may be stored in the COW inode, the folio * belongs to @inode and its data was encrypted (or not) using - * @inode's context (see f2fs_encrypt_one_page()). Read with + * @inode's context (see f2fs_set_bio_crypt_ctx()). Read with * @inode so the post-read decryption decision matches the * folio's owner; otherwise an unencrypted @inode whose COW inode * is encrypted hits a NULL ->i_crypt_info on decryption. -- 2.55.0