[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220331153130.41287-47-jlayton@kernel.org>
Date: Thu, 31 Mar 2022 11:31:22 -0400
From: Jeff Layton <jlayton@...nel.org>
To: ceph-devel@...r.kernel.org
Cc: xiubli@...hat.com, idryomov@...il.com, lhenriques@...e.de,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH v12 46/54] ceph: disable copy offload on encrypted inodes
If we have an encrypted inode, then the client will need to re-encrypt
the contents of the new object. Disable copy offload to or from
encrypted inodes.
Signed-off-by: Jeff Layton <jlayton@...nel.org>
---
fs/ceph/file.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/fs/ceph/file.c b/fs/ceph/file.c
index d8dfb8de4219..29cc65222ddd 100644
--- a/fs/ceph/file.c
+++ b/fs/ceph/file.c
@@ -2528,6 +2528,10 @@ static ssize_t __ceph_copy_file_range(struct file *src_file, loff_t src_off,
return -EOPNOTSUPP;
}
+ /* Every encrypted inode gets its own key, so we can't offload them */
+ if (IS_ENCRYPTED(src_inode) || IS_ENCRYPTED(dst_inode))
+ return -EOPNOTSUPP;
+
if (len < src_ci->i_layout.object_size)
return -EOPNOTSUPP; /* no remote copy will be done */
--
2.35.1
Powered by blists - more mailing lists