Linux-Crypto Archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <oliver.sang@intel.com>
To: Eric Biggers <ebiggers@google.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Karel Balej <balejk@matfyz.cz>,
	Dimitri John Ledkov <dimitri.ledkov@canonical.com>,
	<keyrings@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
	<linux-modules@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [linus:master] [crypto]  203a6763ab: Kernel_panic-not_syncing:Certs_selftest#:pkcs7_verify()=
Date: Mon, 22 Apr 2024 16:05:34 +0800	[thread overview]
Message-ID: <202404221528.51d75177-lkp@intel.com> (raw)



Hello,

we noticed this is a revert patch, but we observed issues in below detail report
that does not happen on parent.

the config has below diff with parent which seems expected.

@@ -720,13 +720,14 @@ CONFIG_MODULE_UNLOAD_TAINT_TRACKING=y
 CONFIG_MODULE_SIG=y
 # CONFIG_MODULE_SIG_FORCE is not set
 CONFIG_MODULE_SIG_ALL=y
-CONFIG_MODULE_SIG_SHA256=y
+CONFIG_MODULE_SIG_SHA1=y
+# CONFIG_MODULE_SIG_SHA256 is not set
 # CONFIG_MODULE_SIG_SHA384 is not set
 # CONFIG_MODULE_SIG_SHA512 is not set
 # CONFIG_MODULE_SIG_SHA3_256 is not set
 # CONFIG_MODULE_SIG_SHA3_384 is not set
 # CONFIG_MODULE_SIG_SHA3_512 is not set
-CONFIG_MODULE_SIG_HASH="sha256"
+CONFIG_MODULE_SIG_HASH="sha1"
 CONFIG_MODULE_COMPRESS_NONE=y
 # CONFIG_MODULE_COMPRESS_GZIP is not set
 # CONFIG_MODULE_COMPRESS_XZ is not set
@@ -6064,7 +6065,7 @@ CONFIG_CRYPTO_MICHAEL_MIC=y
 CONFIG_CRYPTO_POLY1305=m
 # CONFIG_CRYPTO_RMD160 is not set
 CONFIG_CRYPTO_SHA1=y
-CONFIG_CRYPTO_SHA256=y
+CONFIG_CRYPTO_SHA256=m
 CONFIG_CRYPTO_SHA512=y
 CONFIG_CRYPTO_SHA3=y
 CONFIG_CRYPTO_SM3=y

below details just FYI.


kernel test robot noticed "Kernel_panic-not_syncing:Certs_selftest#:pkcs7_verify()=" on:

commit: 203a6763ab699da0568fd2b76303d03bb121abd4 ("Revert "crypto: pkcs7 - remove sha1 support"")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master

[test failed on linus/master 46b28503cdf35e1c34d9d135d91da91d3649ebaf]
[test failed on linux-next/master a35e92ef04c07bd473404b9b73d489aea19a60a8]

in testcase: boot

compiler: clang-17
test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G

(please refer to attached dmesg/kmsg for entire log/backtrace)


+----------------------------------------------------------+------------+------------+
|                                                          | 6a8dbd71a7 | 203a6763ab |
+----------------------------------------------------------+------------+------------+
| Kernel_panic-not_syncing:Certs_selftest#:pkcs7_verify()= | 0          | 18         |
+----------------------------------------------------------+------------+------------+


If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202404221528.51d75177-lkp@intel.com



[  235.982707][ T3437] kmemleak: Automatic memory scanning thread started
[  235.986822][    T1] Key type .fscrypt registered
[  235.987472][    T1] Key type fscrypt-provisioning registered
[  235.988407][    T1] Running certificate verification selftests
[  235.994542][    T1] Loaded X.509 cert 'Certificate verification self-testing key: f58703bb33ce1b73ee02eccdee5b8817518fe3db'
[  235.998172][    T1] Kernel panic - not syncing: Certs selftest 0: pkcs7_verify() = -65
[  235.999259][    T1] CPU: 0 PID: 1 Comm: swapper Tainted: G        W        N 6.8.0-rc1-00082-g203a6763ab69 #1 adf66a20b24f10d450d01d16f8c396f953580a9a
[  236.000960][    T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[  236.002277][    T1] Call Trace:
[ 236.002737][ T1] dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:?) 
[ 236.003344][ T1] dump_stack (kbuild/src/consumer/lib/dump_stack.c:113) 
[ 236.003893][ T1] panic (kbuild/src/consumer/kernel/panic.c:284) 
[ 236.004415][ T1] ? pkcs7_parse_message (kbuild/src/consumer/crypto/asymmetric_keys/pkcs7_parser.c:168) 
[ 236.005101][ T1] fips_signature_selftest (kbuild/src/consumer/crypto/asymmetric_keys/selftest.c:214) 


The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240422/202404221528.51d75177-lkp@intel.com



-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2024-04-22  8:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22  8:05 kernel test robot [this message]
2024-04-22 21:14 ` [linus:master] [crypto] 203a6763ab: Kernel_panic-not_syncing:Certs_selftest#:pkcs7_verify()= Eric Biggers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202404221528.51d75177-lkp@intel.com \
    --to=oliver.sang@intel.com \
    --cc=balejk@matfyz.cz \
    --cc=dimitri.ledkov@canonical.com \
    --cc=ebiggers@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).