kmod-maint May 2014

kmod-maint@lists.fedoraproject.org

3 discussions

[Bug 1071425] New: [abrt] kmod: kmod_module_dependency_symbol_get_crc(): kmod killed by SIGSEGV
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1071425 Bug ID: 1071425 Summary: [abrt] kmod: kmod_module_dependency_symbol_get_crc(): kmod killed by SIGSEGV Product: Fedora Version: 20 Component: kmod Assignee: kmod-maint(a)lists.fedoraproject.org Reporter: campbell.bain(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: jonathan(a)jonmasters.org, kmod-maint(a)lists.fedoraproject.org, msivak(a)redhat.com, vpavlin(a)redhat.com Version-Release number of selected component: kmod-15-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/sbin/depmod -aF /boot/System.map-3.12.9-301.fc20.x86_64 3.12.9-301.fc20.x86_64 crash_function: kmod_module_dependency_symbol_get_crc executable: /usr/bin/kmod kernel: 3.12.9-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (6 frames) #0 kmod_module_dependency_symbol_get_crc at libkmod/libkmod-module.c:2739 #1 depmod_load_module_dependencies at tools/depmod.c:1522 #2 depmod_load_dependencies at tools/depmod.c:1567 #3 depmod_load at tools/depmod.c:1685 #4 do_depmod at tools/depmod.c:2672 #6 _start -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 2

[Bug 1055138] New: [abrt] kmod: __bswap_32(): kmod killed by SIGBUS
by Red Hat Bugzilla 29 Jun '15

29 Jun '15

https://bugzilla.redhat.com/show_bug.cgi?id=1055138 Bug ID: 1055138 Summary: [abrt] kmod: __bswap_32(): kmod killed by SIGBUS Product: Fedora Version: 20 Component: kmod Assignee: kmod-maint(a)lists.fedoraproject.org Reporter: lgraves95(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: jonathan(a)jonmasters.org, kmod-maint(a)lists.fedoraproject.org, msivak(a)redhat.com, vpavlin(a)redhat.com Version-Release number of selected component: kmod-15-1.fc20 Additional info: reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /sbin/modprobe -q -- netdev-eth0 crash_function: __bswap_32 executable: /usr/bin/kmod kernel: 3.12.7-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (6 frames) #0 __bswap_32 at /usr/include/bits/byteswap.h:47 #1 read_long_mm at libkmod/libkmod-index.c:684 #2 index_mm_open at libkmod/libkmod-index.c:815 #3 kmod_load_resources at libkmod/libkmod.c:812 #4 do_modprobe at tools/modprobe.c:908 #6 _start -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 2

[Bug 922201] New: rmmod confused by built-ins
by Red Hat Bugzilla 16 Jun '14

16 Jun '14

Product: Red Hat Enterprise Linux 7 https://bugzilla.redhat.com/show_bug.cgi?id=922201 Bug ID: 922201 Summary: rmmod confused by built-ins Product: Red Hat Enterprise Linux 7 Version: 7.0 Component: kmod Severity: medium Priority: medium Assignee: kay(a)redhat.com Reporter: bmr(a)redhat.com CC: gansalmon(a)Gmail.com, itamar(a)ispbrasil.com.br, jonathan(a)jonmasters.org, kernel-maint(a)redhat.com, kmod-maint(a)lists.fedoraproject.org, madhu.chinakonda(a)gmail.com, msivak(a)redhat.com Depends On: 922187 +++ This bug was initially created as a clone of Bug #922187 +++ Description of problem: Attempting to rmmod something that's not actually built as a module now gives a slightly confusing error: # rmmod loop libkmod: kmod_module_get_holders: could not open '/sys/module/loop/holders': No such file or directory Error: Module loop is in use Previously rmmod from module-init-tools gave a still vague but better "not found" message: # rmmod ext2 ERROR: Module ext2 does not exist in /proc/modules Version-Release number of selected component (if applicable): kmod-* How reproducible: 100% Steps to Reproduce: 1. compile something that can be built as a module as a built-in 2. rmmod $thing Actual results: # rmmod loop libkmod: kmod_module_get_holders: could not open '/sys/module/loop/holders': No such file or directory Error: Module loop is in use Which isn't really true: it's not in use, it's simply built in to vmlinuz so unloading makes no sense. Expected results: modprobe does the right thing: # modprobe -r loop FATAL: Module loop is builtin. Additional info: I know rmmod is the low-level tool and users should be using modprobe -r (or just not messing with this in the first place.. :) but knowledge of modprobe to load and rmmod to unload seems much more widespread among admins and the current behaviour looks at first like a kernel bug (if you didn't realise that there are paths directories missing in /sys/modules/$thing and the module name isn't present in /proc/modules you might think some refcount was broken etc.). --- Additional comment from Bryn M. Reeves on 2013-03-15 13:12:04 EDT --- Error is slightly different from 0:12-1.fc18 but same basic problem: # rmmod loop rmmod: ERROR: could not open '/sys/module/loop/holders': No such file or directory rmmod: ERROR: Module loop is in use -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=NR8Odg50eP&a=cc_unsubscribe

1 9

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

kmod-maint May 2014