[LU-16353] Config variable enable_crypto must not contain special characters Created: 30/Nov/22  Updated: 13/Dec/22  Resolved: 13/Dec/22

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Upstream
Fix Version/s: Lustre 2.16.0

Type: Bug Priority: Minor
Reporter: Neil Brown Assignee: Neil Brown
Resolution: Fixed Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

The "enable_crypto" shell variable  used in autoconf/lustre-core.m4 and config/lustre-build.m4 is sometimes used unquoted, so it is unsafe for it to contain special characters.

It can be set to "embedded llcrypt" which contains a space.  This causes errors when running ./configure.

This appears to be the only enable_foo variable that has this problem.



 Comments   
Comment by Gerrit Updater [ 30/Nov/22 ]

"Neil Brown <neilb@suse.de>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49282
Subject: LU-16353 config: enable_foo variables mustn't contains space
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 899f3ba50df9fc48cd7d28595e77940e8e9baffc

Comment by Gerrit Updater [ 13/Dec/22 ]

"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/49282/
Subject: LU-16353 config: enable_foo variables mustn't contains space
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: c8a33e5322b0675680f8d737f04259799d30aa0e

Comment by Peter Jones [ 13/Dec/22 ]

Landed for 2.16

Generated at Sat Feb 10 03:26:17 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.