Whamcloud - gitweb
LU-12275 sec: force file name encryption policy to null 82/38882/9
authorSebastien Buisson <sbuisson@ddn.com>
Tue, 9 Jun 2020 15:27:53 +0000 (15:27 +0000)
committerOleg Drokin <green@whamcloud.com>
Mon, 20 Jul 2020 05:18:34 +0000 (05:18 +0000)
commit11fcbfa9de4a5170abc2c5df2a6e4e02f0f84268
treebe360446e0341861781dc8adb9c26812dd8fe1f0
parent5f579b16ada4df756e50109004def3c594c0b1a2
LU-12275 sec: force file name encryption policy to null

Force file/directory name encryption policy to null on newly created
inodes. This is required because first implementation step of client
side encryption only supports content encryption, and not names.
This imposes to force usage of embedded llcrypt lib to the detriment
of in-kernel fscrypt lib, even if the kernel provides it.

This patch will have to be reverted when name encryption is
implemented.

Test-Parameters: testlist=sanity-sec envdefinitions=ONLY="36 37 38 39 40 41 42 43 44 45 46 47 48" clientdistro=el8.1 fstype=ldiskfs mdscount=2 mdtcount=4
Test-Parameters: testlist=sanity-sec envdefinitions=ONLY="36 37 38 39 40 41 42 43 44 45 46 47 48" clientdistro=el8.1 fstype=zfs mdscount=2 mdtcount=4
Signed-off-by: Sebastien Buisson <sbuisson@ddn.com>
Change-Id: Ia697a29006507278c218088d7c3a5e5ade620a15
Reviewed-on: https://review.whamcloud.com/38882
Reviewed-by: James Simmons <jsimmons@infradead.org>
Reviewed-by: Andreas Dilger <adilger@whamcloud.com>
Tested-by: jenkins <devops@whamcloud.com>
Tested-by: Maloo <maloo@whamcloud.com>
Reviewed-by: Oleg Drokin <green@whamcloud.com>
libcfs/libcfs/crypto/keysetup.c
libcfs/libcfs/crypto/policy.c
lustre/autoconf/lustre-core.m4