[lustre-devel] Build Dependency Issue in Lustre Mainline Linux

[lustre-devel] Build Dependency Issue in Lustre Mainline Linux

[Chris J Arges]

Just did a fresh git pull --rebase and tried to do 'make deb-pkg' with
an Ubuntu config (which enables lustre). I got the following:

depmod: WARNING: found 2 modules in dependency cycles!
depmod: WARNING:
/home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/drivers/staging/lustre/lnet/lnet/lnet.ko
in dependency cycle!
depmod: WARNING:
/home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/drivers/staging/lustre/lustre/libcfs/libcfs.ko
in dependency cycle!
./scripts/depmod.sh: line 57: 16836 Killed                  "$DEPMOD"
"$@" "$KERNELRELEASE" $SYMBOL_PREFIX
make[2]: *** [_modinst_post] Error 137
make[1]: *** [deb-pkg] Error 2
make: *** [deb-pkg] Error 2

This was building fine in v4.3, so I suspect something after this tag is
causing issue. (My HEAD is at 8e483ed13).

--chris

[lustre-devel] Build Dependency Issue in Lustre Mainline Linux

[Dilger, Andreas]

On 2015/11/05, 13:02, "lustre-devel on behalf of Chris J Arges"
<lustre-devel-bounces at lists.lustre.org on behalf of
chris.j.arges@canonical.com> wrote:

>Just did a fresh git pull --rebase and tried to do 'make deb-pkg' with
>an Ubuntu config (which enables lustre). I got the following:
>
>depmod: WARNING: found 2 modules in dependency cycles!
>depmod: WARNING:
>/home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/driver
>s/staging/lustre/lnet/lnet/lnet.ko
>in dependency cycle!
>depmod: WARNING:
>/home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/driver
>s/staging/lustre/lustre/libcfs/libcfs.ko
>in dependency cycle!
>./scripts/depmod.sh: line 57: 16836 Killed                  "$DEPMOD"
>"$@" "$KERNELRELEASE" $SYMBOL_PREFIX
>make[2]: *** [_modinst_post] Error 137
>make[1]: *** [deb-pkg] Error 2
>make: *** [deb-pkg] Error 2
>
>This was building fine in v4.3, so I suspect something after this tag is
>causing issue. (My HEAD is at 8e483ed13).

Could you run git bisect to find the offending patch?  The error messages
don't really give very much to go on.

Cheers, Andreas
-- 
Andreas Dilger

Lustre Software Architect
Intel High Performance Data Division

[lustre-devel] Build Dependency Issue in Lustre Mainline Linux

[Simmons, James A.]

>Just did a fresh git pull --rebase and tried to do 'make deb-pkg' with
>an Ubuntu config (which enables lustre). I got the following:
>
>depmod: WARNING: found 2 modules in dependency cycles!
>depmod: WARNING:
>/home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/drivers/staging/lustre/lnet/lnet/lnet.ko
>in dependency cycle!
>depmod: WARNING:
>/home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/drivers/staging/lustre/lustre/libcfs/libcfs.ko
>in dependency cycle!
>./scripts/depmod.sh: line 57: 16836 Killed                  "$DEPMOD"

I solved your problem. If you delete IOC_LIBCFS_PING_TEST ioctl case  from libcfs/libcfs/module.c it work again. 
That ioctl has not been is use for some time and it can be removed. What is happening is libcfs_nid2str is being
called which requires lnet.ko now. This is a layer violation. I will be sending a patch very shortly.

[lustre-devel] Build Dependency Issue in Lustre Mainline Linux

[Chris J Arges]

On 11/06/2015 06:10 PM, Simmons, James A. wrote:
> 
>> Just did a fresh git pull --rebase and tried to do 'make deb-pkg' with
>> an Ubuntu config (which enables lustre). I got the following:
>>
>> depmod: WARNING: found 2 modules in dependency cycles!
>> depmod: WARNING:
>> /home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/drivers/staging/lustre/lnet/lnet/lnet.ko
>> in dependency cycle!
>> depmod: WARNING:
>> /home/arges/src/kernel/linux/./debian/tmp/lib/modules/4.3.0+/kernel/drivers/staging/lustre/lustre/libcfs/libcfs.ko
>> in dependency cycle!
>> ./scripts/depmod.sh: line 57: 16836 Killed                  "$DEPMOD"
> 
> I solved your problem. If you delete IOC_LIBCFS_PING_TEST ioctl case  from libcfs/libcfs/module.c it work again. 
> That ioctl has not been is use for some time and it can be removed. What is happening is libcfs_nid2str is being
> called which requires lnet.ko now. This is a layer violation. I will be sending a patch very shortly.
> 

Thanks, good to hear.
--chris