[LU-4750] lustre 2.5.1-rc fails to compile from source ( redhat sources ) Created: 11/Mar/14  Updated: 22/Mar/14  Resolved: 22/Mar/14

Status: Resolved
Project: Lustre
Component/s: None
Affects Version/s: Lustre 2.5.1
Fix Version/s: None

Type: Bug Priority: Blocker
Reporter: James Beal Assignee: Minh Diep
Resolution: Cannot Reproduce Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 13076

 Description   

I believe compilation from source is being effected by https://bugzilla.redhat.com/show_bug.cgi?id=613568

With a clean set of source linux-2.6.32-431.5.1.el6 with or without lustre patches applied but using the config file from 2.5.1-rc1

cp /local/lustre-2.5.1-RC/lustre-2.5.56/lustre/kernel_patches/kernel_configs/kernel-2.6.32-2.6-rhel6-x86_64.config ./.config

CC crypto/signature/ksign-publickey.o
crypto/signature/ksign-publickey.c:2:17: error: key.h: No such file or directory
crypto/signature/ksign-publickey.c: In function ‘ksign_init’:
crypto/signature/ksign-publickey.c:10: error: ‘ksign_def_public_key’ undeclared (first use in this function)
crypto/signature/ksign-publickey.c:10: error: (Each undeclared identifier is reported only once
crypto/signature/ksign-publickey.c:10: error: for each function it appears in.)
crypto/signature/ksign-publickey.c:11: error: ‘ksign_def_public_key_size’ undeclared (first use in this function)
make[2]: *** [crypto/signature/ksign-publickey.o] Error 1
make[1]: *** [crypto/signature] Error 2
make: *** [crypto] Error 2

From http://scientificlinuxforum.org/index.php?showtopic=1324

"run make menuconfig.
1) Select "Enable loadable module support", then "Module signature verification (EXPERIMENTAL)". Disable it.
2) Then go back to the main menu, select "Cryptographic API" then "In-kernel signature checker (EXPERIMENTAL)" and disable that one too.
Then go back again, save your config and make your kernel. At least, it will pass this phase successfully."

Which gives this diff:

diff .config .config.orig
4c4
< # Tue Mar 11 14:53:15 2014

> # Tue Mar 11 09:06:11 2014
215c215,216
< # CONFIG_MODULE_SIG is not set

> CONFIG_MODULE_SIG=y
> # CONFIG_MODULE_SIG_FORCE is not set
4544c4545,4546
< # CONFIG_CRYPTO_SIGNATURE is not set

> CONFIG_CRYPTO_SIGNATURE=y
> CONFIG_CRYPTO_SIGNATURE_DSA=y



 Comments   
Comment by Peter Jones [ 11/Mar/14 ]

Minh

Could you please look into this one?

Thanks

Peter

Comment by James A Simmons [ 11/Mar/14 ]

While we are at it I also found one bug that prevented b2_5 from building. In libcfs/include/libcfs/posix/libcfs.h defines

struct shrinker {
;
};

Some versions of gcc don't like this. So I got around this problem by defining struct shrinker as

struct shrinker {
int pad;
}

Comment by Minh Diep [ 17/Mar/14 ]

build failed with the change above. it complains about module not signed

http://build.whamcloud.com/job/lustre-reviews/22530/arch=x86_64,build_type=server,distro=el6,ib_stack=inkernel/console

431.5.1.el6_lustre.gf478ed2.x86_64/boot/vmlinuz-2.6.32-431.5.1.el6_lustre.gf478ed2.x86_64
+ mkdir -p /var/lib/jenkins/workspace/lustre-reviews/arch/x86_64/build_type/server/distro/el6/ib_stack/inkernel/BUILD/BUILDROOT/kernel-2.6.32-431.5.1.el6_lustre.gf478ed2.x86_64/lib/modules/2.6.32-431.5.1.el6_lustre.gf478ed2.x86_64
+ '[' x86_64 '!=' s390 -o '' '!=' kdump ']'
+ make -s ARCH=x86_64 INSTALL_MOD_PATH=/var/lib/jenkins/workspace/lustre-reviews/arch/x86_64/build_type/server/distro/el6/ib_stack/inkernel/BUILD/BUILDROOT/kernel-2.6.32-431.5.1.el6_lustre.gf478ed2.x86_64 modules_install KERNELRELEASE=2.6.32-431.5.1.el6_lustre.gf478ed2.x86_64 mod-fw=
++ grep module.sig
+++ find fs/ -name '*.ko'
+++ head -n 1
++ readelf -n fs/nfs/nfs_layout_nfsv41_files.ko
+ '[' -z '' ']'
+ echo 'ERROR: modules are NOT signed'
ERROR: modules are NOT signed
+ exit 1
error: Bad exit status from /var/tmp/rpm-tmp.ThNEOc (%b

Comment by Minh Diep [ 18/Mar/14 ]

Hi James,

We were unable to reproduce your error. Could you describe all the steps that lead to the error?

Thanks
-Minh

Comment by James Beal [ 22/Mar/14 ]

I have tried with 2.5.1 and it does not occur for me with that version...

Sorry for the confusion

Comment by Peter Jones [ 22/Mar/14 ]

ok - thanks James!

Generated at Sat Feb 10 01:45:31 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.