Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> writes: > On Mon, Oct 11, 2021 at 10:34:11AM +0200, Nicolai Stange wrote: >> >> In order to keep a FIPS certification manageable in terms of scope, >> we're looking for a way to disable everything under drivers/crypto iff >> fips_enabled == 1. The most convenient way to achieve this downstream >> would be to add dummy entries to testmgr.c like so: > > How about testing based on the flag CRYPTO_ALG_KERN_DRIVER_ONLY? > That flag is meant to correspond to pretty much exactly > drivers/crypto. Hmm, I checked a couple of crypto/drivers and it seems like not all are setting this flag: random examples would include cavium/nitrox/, chelsio/, padlock*.c, vmx/, ... Many thanks! Nicolai -- SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg), GF: Felix Imendörffer