Re: [kbuild-all] Re: kismet: WARNING: unmet direct dependencies detected for CRYPTO_DEV_FSL_CAAM_BLOB_GEN when selected by TRUSTED_KEYS_CAAM

[Yujie Liu]

Hi Ahmad,

On 5/28/2022 16:00, Ahmad Fatoum wrote:
> Hi,
>
> On 28.05.22 09:42, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   9d004b2f4fea97cde123e7f1939b80e77bf2e695
> > commit: e9c5048c2de1913d0bcd589bc1487810c2e24bc1 KEYS: trusted: Introduce support for NXP CAAM-based trusted keys
> > date:   5 days ago
> > config: (https://download.01.org/0day-ci/archive/20220528/202205281527.o6zXpTYo-lkp@xxxxxxxxx/config)
> > reproduce:
> >          # https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e9c5048c2de1913d0bcd589bc1487810c2e24bc1
> >          git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> >          git fetch --no-tags linus master
> >          git checkout e9c5048c2de1913d0bcd589bc1487810c2e24bc1
> >          # 1. reproduce by kismet
> >             # install kmax per https://github.com/paulgazz/kmax/blob/master/README.md
> >             kismet --linux-ksrc=linux --selectees CONFIG_CRYPTO_DEV_FSL_CAAM_BLOB_GEN --selectors CONFIG_TRUSTED_KEYS_CAAM -a=arm64
> >          # 2. reproduce by make
> >             # save the config file to linux source tree
> >             cd linux
> >             make ARCH=arm64 olddefconfig
> >
> > If you fix the issue, kindly add following tag where applicable
> > Reported-by: kernel test robot <lkp@xxxxxxxxx>
> >
> >
> > kismet warnings: (new ones prefixed by >>)
> > > > kismet: WARNING: unmet direct dependencies detected for CRYPTO_DEV_FSL_CAAM_BLOB_GEN when selected by TRUSTED_KEYS_CAAM
>
> The referenced config file doesn't have anything CAAM related enabled.
>
> I looked again at the Kconfig and CRYPTO_DEV_FSL_CAAM_BLOB_GEN depends on
> CRYPTO_DEV_FSL_CAAM_JR. TRUSTED_KEYS_CAAM depends on
> CRYPTO_DEV_FSL_CAAM_JR >= TRUSTED_KEYS and only then selects
> CRYPTO_DEV_FSL_CAAM_BLOB_GEN, which still looks correct to me.
>
> Could one of the authors elaborate what issue is being reported here?

We have rechecked this report and it is indeed a false alarm. Sorry for the inconvenience.

kismet is a new tool for analyzing kconfig dependency, which is enabled in our test robot
recently, so there may still be some issues in the test flow. We have found the root cause
of this false alarm and fixed it, thanks.

Best Regards,
Yujie

> Cheers,
> Ahmad
>
> >