[LU-20279] Build scripts don't copy ext4/crypto.c if EXT4_CRYPTO is not set

• Type: Bug
• Resolution: Unresolved
• Priority: Medium
• Fix Version/s: Lustre 2.18.0
• Affects Version/s: Lustre 2.18.0
• Severity: 3
• Assignee: Alexey Lyashkov
• Reporter: Oleg Drokin

Description

Looks like when EXT4_CRYPTO is not set, we do not copy fs/ext4/crypto.c for ldiskfs and then whatever patch might need it - fails to apply.

This was exposed by this patch in particular: https://review.whamcloud.com/c/fs/lustre-release/+/65426

config/lustre-build-ldiskfs.m4:

                LB2_TEST_CHECK_CONFIG_IM([FS_ENCRYPTION], [
                        EXT4_CRYPTO=],[
                        EXT4_CRYPTO='%/crypto.c'])
                LB2_TEST_CHECK_CONFIG_IM([FS_VERITY], [
                        EXT4_VERITY=],[
                        EXT4_VERITY='%/verity.c'])

ldiskfs/Makefile.in:

backfs_sources := $(filter-out %.mod.c $(backfs_unit_tests) @EXT4_CRYPTO@ @EXT4_VERITY@,$(wildcard @EXT4_SRC_DIR@/*.c)) 

Looks like similar problem is with verity?