# git rev-parse -q --verify 67ec8cdf29971677b2fb4b6d92871eb5d5e95597^{commit}
# git fetch -q -n -f git://fs.ozlabs.ibm.com/kernel/crypto master
warning: The last gc run reported the following. Please correct the root cause
and remove .git/gc.log.
Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.

# git rev-parse -q --verify 67ec8cdf29971677b2fb4b6d92871eb5d5e95597^{commit}
67ec8cdf29971677b2fb4b6d92871eb5d5e95597
# git checkout -q -f -B kisskb 67ec8cdf29971677b2fb4b6d92871eb5d5e95597
# git clean -qxdf
# < git log -1
# commit 67ec8cdf29971677b2fb4b6d92871eb5d5e95597
# Author: Herbert Xu <herbert@gondor.apana.org.au>
# Date:   Wed May 22 13:37:54 2024 +0800
# 
#     hwrng: core - Remove add_early_randomness
#     
#     A potential deadlock was reported with the config file at
#     
#     https://web.archive.org/web/20240522052129/https://0x0.st/XPN_.txt
#     
#     In this particular configuration, the deadlock doesn't exist because
#     the warning triggered at a point before modules were even available.
#     However, the deadlock can be real because any module loaded would
#     invoke async_synchronize_full.
#     
#     The issue is spurious for software crypto algorithms which aren't
#     themselves involved in async probing.  However, it would be hard to
#     avoid for a PCI crypto driver using async probing.
#     
#     In this particular call trace, the problem is easily avoided because
#     the only reason the module is being requested during probing is the
#     add_early_randomness call in the hwrng core.  This feature is
#     vestigial since there is now a kernel thread dedicated to doing
#     exactly this.
#     
#     So remove add_early_randomness as it is no longer needed.
#     
#     Reported-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
#     Reported-by: Eric Biggers <ebiggers@kernel.org>
#     Fixes: 1b6d7f9eb150 ("tpm: add session encryption protection to tpm2_get_random()")
#     Link: https://lore.kernel.org/r/119dc5ed-f159-41be-9dda-1a056f29888d@notapiano/
#     Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
#     Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
#     Tested-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
#     Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
# < /opt/cross/kisskb/korg/gcc-8.5.0-nolibc/x86_64-linux/bin/x86_64-linux-gcc --version
# < /opt/cross/kisskb/korg/gcc-8.5.0-nolibc/x86_64-linux/bin/x86_64-linux-ld --version
# < git log --format=%s --max-count=1 67ec8cdf29971677b2fb4b6d92871eb5d5e95597
# make -s -j 160 ARCH=x86_64 O=/kisskb/build/crypto_allmodconfig_x86_64-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.5.0-nolibc/x86_64-linux/bin/x86_64-linux-  allmodconfig
# Added to kconfig CONFIG_BUILD_DOCSRC=n
# Added to kconfig CONFIG_MODULE_SIG=n
# Added to kconfig CONFIG_SAMPLES=n
# Added to kconfig CONFIG_GCC_PLUGINS=n
# Added to kconfig 
# < make -s -j 160 ARCH=x86_64 O=/kisskb/build/crypto_allmodconfig_x86_64-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.5.0-nolibc/x86_64-linux/bin/x86_64-linux-  help
# make -s -j 160 ARCH=x86_64 O=/kisskb/build/crypto_allmodconfig_x86_64-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.5.0-nolibc/x86_64-linux/bin/x86_64-linux-  olddefconfig
# make -s -j 160 ARCH=x86_64 O=/kisskb/build/crypto_allmodconfig_x86_64-gcc8 CROSS_COMPILE=/opt/cross/kisskb/korg/gcc-8.5.0-nolibc/x86_64-linux/bin/x86_64-linux-  
Completed OK
# rm -rf /kisskb/build/crypto_allmodconfig_x86_64-gcc8
# Build took: 0:19:53.884492