Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1260731 > unrolled thread
| Started by | Valdis Kletnieks <Valdis.Kletnieks@vt.edu> |
|---|---|
| First post | 2015-11-02 16:50 +0100 |
| Last post | 2015-11-09 22:50 +0100 |
| Articles | 4 — 4 participants |
Back to article view | Back to linux.kernel
next-20151101 - depmod issues with Lustre modules Valdis Kletnieks <Valdis.Kletnieks@vt.edu> - 2015-11-02 16:50 +0100
Re: next-20151101 - depmod issues with Lustre modules Linus Torvalds <torvalds@linux-foundation.org> - 2015-11-07 23:40 +0100
Re: next-20151101 - depmod issues with Lustre modules Stephen Rothwell <sfr@canb.auug.org.au> - 2015-11-12 23:20 +0100
RE: [lustre-devel] next-20151101 - depmod issues with Lustre modules "Simmons, James A." <simmonsja@ornl.gov> - 2015-11-09 22:50 +0100
| From | Valdis Kletnieks <Valdis.Kletnieks@vt.edu> |
|---|---|
| Date | 2015-11-02 16:50 +0100 |
| Subject | next-20151101 - depmod issues with Lustre modules |
| Message-ID | <qqpwR-745-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
next-20151101 compiles fine, but depmod has a cow: depmod: ERROR: Found 2 modules in dependency cycles! depmod: ERROR: Cycle detected: lnet -> libcfs -> lnet Sorry, not sure which commit(s) introduced the issue. next-20151022 was OK.
[toc] | [next] | [standalone]
| From | Linus Torvalds <torvalds@linux-foundation.org> |
|---|---|
| Date | 2015-11-07 23:40 +0100 |
| Message-ID | <qskjo-8jg-9@gated-at.bofh.it> |
| In reply to | #1260731 |
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/
[toc] | [prev] | [next] | [standalone]
| From | Stephen Rothwell <sfr@canb.auug.org.au> |
|---|---|
| Date | 2015-11-12 23:20 +0100 |
| Message-ID | <qu8nL-6oo-15@gated-at.bofh.it> |
| In reply to | #1264940 |
Hi Linus, On Sat, 7 Nov 2015 14:30:44 -0800 Linus Torvalds <torvalds@linux-foundation.org> wrote: > > I do wonder if linux-next could perhaps do some modprobe testing too? I have added an x86_64 allmodconfig modules_install to my end-of-day-before-release builds. Is that useful/sufficient? It seems to work fine at the moment. -- Cheers, Stephen Rothwell sfr@canb.auug.org.au -- 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/
[toc] | [prev] | [next] | [standalone]
| From | "Simmons, James A." <simmonsja@ornl.gov> |
|---|---|
| Date | 2015-11-09 22:50 +0100 |
| Subject | RE: [lustre-devel] next-20151101 - depmod issues with Lustre modules |
| Message-ID | <qt2u6-3M6-27@gated-at.bofh.it> |
| In reply to | #1260731 |
DQo+UmVwcm9kdWNlZCBvbiBtYWlubGluZSB2NC4zLTkwMzgtZzI3ZWI0MjdiZGMwOTYwIHdpdGgN Cj5BcmNoIExpbnV4IGRlZmF1bHQgY29uZmlnIChhdHRhY2hlZCk6DQo+DQo+ZGVwbW9kOiBFUlJP UjogRm91bmQgMiBtb2R1bGVzIGluIGRlcGVuZGVuY3kgY3ljbGVzIQ0KPmRlcG1vZDogRVJST1I6 IEN5Y2xlIGRldGVjdGVkOiBsbmV0IC0+IGxpYmNmcyAtPiBsbmV0DQo+bWFrZTogKioqIFtfbW9k aW5zdF9wb3N0XSBFcnJvciAxDQoNCkkgc3VibWl0dGVkIGEgcGF0Y2ggKHN0YWdpbmc6IGx1c3Ry ZTogcmVtb3ZlIElPQ19MSUJDRlNfUElOR19URVNUIGlvY3RsKSB0byBmaXggdGhpcy4NCkl0IHNo b3VsZCBiZSBtZXJnZWQgc29vbi4NCg== -- 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/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web