https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-15406 Lustre <p>To validate the port of fscrypt for RHEL8 which is from a 5.4 kernel I changed the build system to automatically use the native fscrypt for the Ubuntu 5.4 kernel. In theory it should have identical results. This is not the case which you can see the test failures with patch <a href="https://review.whamcloud.com/#/c/45907" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/#/c/45907</a>.</p> Ubuntu20 client running 5.4 kernel. LU-15406

Using the native fscrypt for Ubuntu20 5.4 kernel fails several migration test

Bug Critical Resolved Fixed Sebastien Buisson James A Simmons Mon, 3 Jan 2022 14:25:27 +0000 Mon, 21 Mar 2022 18:48:28 +0000 Tue, 18 Jan 2022 13:59:12 +0000 Lustre 2.15.0 Lustre 2.15.0 0 5 <p>Seb</p> <p>Could you please investigate?</p> <p>Thanks</p> <p>Peter</p> <p>"Sebastien Buisson &lt;sbuisson@ddn.com&gt;" uploaded a new patch: <a href="https://review.whamcloud.com/45987" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/45987</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-15406" title="Using the native fscrypt for Ubuntu20 5.4 kernel fails several migration test" class="issue-link" data-issue-key="LU-15406"><del>LU-15406</del></a> sec: fix in-kernel fscrypt support<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: 1<br/> Commit: 6eda4575b6f9bf678c2036d25d500f9e3d9ec335</p> <p>This problem seen with the in-kernel fscrypt library is limited to file migration (sanity-sec test_52 and test_59b). In this use case, Lustre creates a temporary, volatile file to migrate data. For encrypted files, we explicitly set the encryption context of the volatile file (directly on server side) to be the same as the original file, so that data is encrypted with the same key. Problem is the encryption context of the original file is simply not retrieved when using the in-kernel fscrypt lib. So the volatile file has its own encryption context, which makes the migrated content encrypted with a different key. And this key is trashed. As a consequence, the content of the file after migration cannot just be decrypted properly.</p> <p>I have pushed <a href="https://review.whamcloud.com/45987" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/45987</a> to fix this issue.</p> <p>Thank you. I will test.</p> <p>"Oleg Drokin &lt;green@whamcloud.com&gt;" merged in patch <a href="https://review.whamcloud.com/45987/" class="external-link" target="_blank" rel="nofollow noopener">https://review.whamcloud.com/45987/</a><br/> Subject: <a href="https://jira.whamcloud.com/browse/LU-15406" title="Using the native fscrypt for Ubuntu20 5.4 kernel fails several migration test" class="issue-link" data-issue-key="LU-15406"><del>LU-15406</del></a> sec: fix in-kernel fscrypt support<br/> Project: fs/lustre-release<br/> Branch: master<br/> Current Patch Set: <br/> Commit: 2169aed82a32df47be9aef2f249178ede6c7fadd</p> <p>Landed for 2.15</p> Related LU-13717 Development Rank 1|i02dj3: Rank (Obsolete) 9223372036854775807 Severity