[LU-1599] Error inserting padlock_sha.ko when load lnet-selftest

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.3.0
• Type: Bug
• Priority: Major
• Reporter: Doug Oucharek (Inactive)
• Assignee: WC Triage
• Resolution: Not a Bug

Environment

CentOS 6.2

• Severity: 3

Description

After building the master branch (Jul. 4/12), I wanted to run an LNet Selftest. When I enter "modprobe lnet-selftest", there is about a 10 second pause before the load completes. When I look at the logs to see why, I see this:

Jul 4 13:31:50 localhost kernel: LNet: HW CPU cores: 2, npartitions: 1
Jul 4 13:31:50 localhost kernel: alg: No test for crc32 (crc32-table)
Jul 4 13:31:50 localhost kernel: alg: No test for adler32 (adler32-zlib)
Jul 4 13:31:50 localhost kernel: alg: No test for crc32 (crc32-pclmul)
Jul 4 13:31:54 localhost kernel: padlock: VIA PadLock Hash Engine not detected.
Jul 4 13:31:54 localhost modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32.lustre23/kernel/drivers/crypto/padlock-sha.ko): No such device
Jul 4 13:31:59 localhost kernel: LNet: Added LNI 10.211.55.16@tcp [8/256/0/180]
Jul 4 13:31:59 localhost kernel: LNet: Accept secure, port 988

It seems to be tripping up on loading padlock_sha.ko.

This bug appears to have been introduced by LU-1201.

Comments

[Alexander Boyko]

>>there is about a 10 second pause before the load completes
because libcfs run performance test for supported crypto hash algo. This data should be used for best default algorithm selection for osc-ost interaction.
>>padlock: VIA PadLock Hash Engine not detected.
The messages come up because you don't have hardware support for encryption.
>>Jul 4 13:31:54 localhost modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32.lustre23/kernel/drivers/crypto/padlock-sha.ko): No such device
I don`t know who use sha algo for cksum. If you insmod only libcfs.ko no padlock-sha.ko error at dmesg log for my SL6.1.

I have one assumption:
when performance test starts for sha algo, kernel crypto hash api try to load all *sha.ko, including padlock-sha.ko but this is wrong if you get VIA PadLock Hash Engine not detected. May be this relate to distro problem.

[Vinod Kumar (Inactive)]

We are seeing a similar issue.

Lustre-2.4.1
RHEL-6.4

Nov 18 07:03:31 st61 modprobe: FATAL: Error inserting crc32c_intel
(/lib/modules/2.6.32-358.18.1.el6_lustre.x86_64/kernel/arch/x86/crypto/crc32c-intel.ko):
No such device
Nov 18 07:03:31 st61 kernel: alg: No test for crc32 (crc32-table)
Nov 18 07:03:31 st61 kernel: alg: No test for adler32 (adler32-zlib)
Nov 18 07:03:35 st61 kernel: padlock: VIA PadLock Hash Engine not detected.
Nov 18 07:03:35 st61 modprobe: FATAL: Error inserting padlock_sha
(/lib/modules/2.6.32-358.18.1.el6_lustre.x86_64/kernel/drivers/crypto/padlock-sha.ko):
No such device
Nov 18 07:03:39 st61 kernel: Lustre: Lustre: Build Version:
2.4.1-RC2--PRISTINE-2.6.32-358.18.1.el6_lustre.x86_64

This happens when we are loading Lustre on MDS / OST servers.
Also we are using IB for Lnet.

[Alexander Boyko]

Nothing bad really happens. padlock-sha.ko was not loaded cause you have no VIA PadLock Hash Engine hardware. If this fatal message confuse, you can blacklist padlock-sha module.