kmod-maint July 2014

kmod-maint@lists.fedoraproject.org

2 participants
13 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 1122700] New: sysctl.conf / sysctl.conf.d settings not read when modules are loaded (one result being that libvirt bridged networking with NetworkManager does not work correctly)
by Red Hat Bugzilla 12 Aug '14

12 Aug '14

https://bugzilla.redhat.com/show_bug.cgi?id=1122700 Bug ID: 1122700 Summary: sysctl.conf / sysctl.conf.d settings not read when modules are loaded (one result being that libvirt bridged networking with NetworkManager does not work correctly) Product: Red Hat Enterprise Linux 7 Version: 7.0 Component: kmod Severity: high Priority: low Assignee: dshea(a)redhat.com Reporter: awilliam(a)redhat.com QA Contact: kernel-qe(a)redhat.com CC: arapov(a)gmail.com, awilliam(a)redhat.com, bburke264(a)gmail.com, dcbw(a)redhat.com, djasa(a)redhat.com, dwmw2(a)infradead.org, edgar.hoch(a)ims.uni-stuttgart.de, extras-qa(a)fedoraproject.org, hancock(a)sedsystems.ca, hiroshi01.itani(a)g.softbank.co.jp, jonathan(a)jonmasters.org, jwboyer(a)redhat.com, kmod-maint(a)lists.fedoraproject.org, laine(a)redhat.com, m.koshelev(a)gmail.com, mschuppe(a)redhat.com, msivak(a)redhat.com, notting(a)splat.cc, rc556677(a)outlook.com, sjenning(a)redhat.com, vpavlin(a)redhat.com, zbyszek(a)in.waw.pl Depends On: 634736 +++ This bug was initially created as a clone of Bug #634736 +++ Description of problem: On a system that uses NetworkManager and has bridges, when system boot is complete the settings of net.bridge.bridge-nf-call-iptables , net.bridge.bridge-nf-call-ip6tables and net.bridge.bridge-nf-call-arptables are always "1", despite /usr/lib/sysctl.d/00-system.conf attempting to set them to "0". This prevents bridged connections to virtual machines working almost at all (if you set a static IP address a VM can ping numeric IPs, but that's about all). The problem, which is rather well known by now, is that the settings only actually exist once the 'bridge' module is loaded, but the systemd service which applies these settings, systemd-sysctl.service , runs before the module is loaded. There is no mechanism in the kernel, kmod, or systemd which would cause sysctl settings to be re-read and re-applied when a kernel module is loaded. The old 'network' service has a hack for this. It runs the function apply_sysctl() from /etc/init.d/functions a couple of times when bringing up interfaces. Hence folks using bridging with the old network service didn't see this problem. NetworkManager does not have an equivalent hack, however. The 'bridge' incarnation of this problem is the one people are always running into, but in theory at least it is a generic problem, it could affect any other module with tunable settings. There are various proposals for fixing this in the Fedora bug, notably from Edgar Hoch: EH#1: Implement a hack in NetworkManager similar to the one in the old network service: "I have created a dispatcher file for NetworkManager that reloads the kernel parameter after change of a network interface." https://bugzilla.redhat.com/show_bug.cgi?id=634736#c5 EH#2: "A real solution - the best? - should be that every kernel module will check for parameters in sysctl config files immediate after loading the kernel module. This would avoid the con listed above." https://bugzilla.redhat.com/show_bug.cgi?id=634736#c7 EH#3: "For solving the general problem, I have the following idea: - The kernel should remember parameters set by sysctl even if this parameter does not exist in the kernel at the time when the parameter was set. When the parameter is created later (for example by loading a module), the kernel should check the list of previous loaded parameters and if the parameter is found, this value should be used as default instead of other defaults. This solution needs changes in the kernel. But it sets the values at the right time (only the kernel knows when a parameter is created) and it has less overhead than other solutions (for example like checking sysctl config files after every module load)." https://bugzilla.redhat.com/show_bug.cgi?id=634736#c9 The sysctl.d manpage explicitly notes the 'bridge' incarnation of this bug, and suggests two other approaches: SYSCTL#1: create a udev rule ACTION=="add", SUBSYSTEM=="module", KERNEL=="bridge", RUN+="/usr/lib/systemd/systemd-sysctl --prefix=/proc/sys/net/bridge" SYSCTL#2: cause the 'bridge' module to be loaded statically very early in boot by listing it in a file in /usr/lib/modules-load.d/ Both of these approaches are specific to the 'bridge' incarnation of the problem. However we decide to do it, at *least* the bridge incarnation of this issue really needs to be solved; if you're trying to set up libvirt bridged networking with NetworkManager you *will* trip over this bug, and it's quite frustrating to diagnose until you stumble across an old Fedora guide that mentions the sysctl parameters or something. RHEL 7 and all now-supported Fedora versions are basically identical so far as this bug goes, so the same fix can and probably should be used for both. There's a whole other mess related to these parameters for RHEL 6 - see https://bugzilla.redhat.com/show_bug.cgi?id=919472 , but don't dive in too deep - but thankfully that should not be at all relevant to RHEL 7, as our attempt to override the defaults is no longer in /etc/sysctl.conf . Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=634736 [Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded -- 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=3fgocUr9KN&a=cc_unsubscribe

1 1

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 25 Jul '14

25 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=634736 Cole Robinson <crobinso(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|19 |21 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 24 Jul '14

24 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=634736 --- Comment #20 from Bill Nottingham <notting(a)splat.cc> --- systemd automatically reapplies for anything loaded by systemd-modules-load.service; it also has: # Apply sysctl variables to network devices (and only to those) as they appear. ACTION=="add", SUBSYSTEM=="net", KERNEL!="lo", RUN+="/usr/lib/systemd/systemd-sysctl --prefix=/proc/sys/net/ipv4/conf/$name --prefix=/proc/sys/net/ipv4/neigh/$name --prefix=/proc/sys/net/ipv6/conf/$name --prefix=/proc/sys/net/ipv6/neigh/$name" for network devices. It doesn't handle any cases outside of that. Arguably, I could see modules registering their sysctl range somehow so you could just do: ACTION=="add", SUBSYSTEM=="module", RUN+="/usr/lib/systemd/systemd-sysctl --prefix=/proc/sys/$kernel" (replace $kernel with whatever the variable is) But that requires kernel changes. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 23 Jul '14

23 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=634736 Adam Williamson (Red Hat) <awilliam(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1122700 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=1122700 [Bug 1122700] sysctl.conf / sysctl.conf.d settings not read when modules are loaded (one result being that libvirt bridged networking with NetworkManager does not work correctly) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 23 Jul '14

23 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=634736 Adam Williamson (Red Hat) <awilliam(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zbyszek(a)in.waw.pl --- Comment #19 from Adam Williamson (Red Hat) <awilliam(a)redhat.com> --- sysctl.d manpage notes: "Many sysctl parameters only become available when certain kernel modules are loaded. Modules are usually loaded on demand, e.g. when certain hardware is plugged in or network brought up. This means that systemd-sysctl.service(8) which runs during early boot will not configure such parameters if they become available after it has run. To set such parameters, it is recommended to add an udev(7) rule to set those parameters when they become available." The example udev rule given for bridging is: /etc/udev/rules.d/99-bridge.conf: ACTION=="add", SUBSYSTEM=="module", KERNEL=="bridge", RUN+="/usr/lib/systemd/systemd-sysctl --prefix=/proc/sys/net/bridge" so...possibly we should be shipping such a udev rule ourselves. Let's bring in the systemd folks, why not, everyone else is at the party already... -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 23 Jul '14

23 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=634736 Adam Williamson (Red Hat) <awilliam(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |notting(a)splat.cc --- Comment #18 from Adam Williamson (Red Hat) <awilliam(a)redhat.com> --- Hrm. In a RHEL report on the same bug, Bill Nottingham noted: "- we have systemd support for applying keys on module load (in fact, systemd is what applies keys at boot time now, rather than a script) So, starting in F-18, all the system defaults (such as this) have moved to /usr/lib/sysctl.d/00-system.conf, which is read by systemd and applied at boot (or after any necessary modules have loaded)." which sounds like systemd should be taking care of this, but it doesn't seem to be. CCing Bill: can you elaborate? Should systemd know to apply these settings when the 'bridge' module is loaded? Is there a bug in systemd? -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 23 Jul '14

23 Jul '14

1 0

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 23 Jul '14

23 Jul '14

https://bugzilla.redhat.com/show_bug.cgi?id=634736 Adam Williamson (Red Hat) <awilliam(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|net.bridge.bridge-nf-call-i |sysctl.conf / sysctl.conf.d |ptables setting in |settings not read when |sysctl.conf doesn't match |modules are loaded |setting in kernel | -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

kmod-maint July 2014