Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754531AbbKGWaq (ORCPT ); Sat, 7 Nov 2015 17:30:46 -0500 Received: from mail-io0-f170.google.com ([209.85.223.170]:33838 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752400AbbKGWao (ORCPT ); Sat, 7 Nov 2015 17:30:44 -0500 MIME-Version: 1.0 In-Reply-To: References: <8398.1446478793@turing-police.cc.vt.edu> Date: Sat, 7 Nov 2015 14:30:44 -0800 X-Google-Sender-Auth: kP38SDQG456SDk96xImuSBOmmWc Message-ID: Subject: Re: next-20151101 - depmod issues with Lustre modules From: Linus Torvalds To: Dmitry Safonov <0x7f454c46@gmail.com>, James Simmons , Greg Kroah-Hartman , Stephen Rothwell Cc: Valdis Kletnieks , Oleg Drokin , Andreas Dilger , Linux Kernel Mailing List , lustre-devel@lists.lustre.org Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1384 Lines: 41 On Sat, Nov 7, 2015 at 12:37 PM, Dmitry Safonov <0x7f454c46@gmail.com> wrote: > Reproduced on mainline v4.3-9038-g27eb427bdc0960 with > Arch Linux default config (attached): > > depmod: ERROR: Found 2 modules in dependency cycles! > depmod: ERROR: Cycle detected: lnet -> libcfs -> lnet > make: *** [_modinst_post] Error 1 The reason seems to be that - lnet.ko provides the following functions needed by libcfs.ko: libcfs_next_nidstring libcfs_nid2str_r - libcfs.ko provides the following functions needed by lnet.ko: libcfs_debug libcfs_debug_msg libcfs_deregister_ioctl libcfs_register_ioctl libcfs_subsystem_debug lustre_insert_debugfs but I may have messed up something. Anyway, the problem seems to be that - insanely - lnet.ko provides those libcfs nid handling functions. They should be in libcfs, as far as I can tell, just judging by the name. Also judging by the use. The cause seems to be commit 47ca6ec2673e ("staging: lustre: move nidstring handling to LNet layer") by James Simmons. I do wonder if linux-next could perhaps do some modprobe testing too? Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/