kmod-maint February 2015

kmod-maint@lists.fedoraproject.org

2 participants
11 discussions

[Bug 1130210] New: [abrt] kmod: free(): kmod killed by SIGABRT
by Red Hat Bugzilla 19 Jul '16

19 Jul '16

https://bugzilla.redhat.com/show_bug.cgi?id=1130210 Bug ID: 1130210 Summary: [abrt] kmod: free(): kmod killed by SIGABRT Product: Fedora Version: rawhide Component: kmod Assignee: kmod-maint(a)lists.fedoraproject.org Reporter: mail(a)stefanringel.de 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-18-2.fc22 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: depmod -ae -F /boot/System.map-3.17.0-0.rc0.git4.2.fc22.x86_64 3.17.0-0.rc0.git4.2.fc22.x86_64 crash_function: free executable: /usr/bin/kmod kernel: 3.16.0-1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (5 frames) #4 free at /lib64/libc.so.6 #5 index_destroy #12 output_deps_bin #13 do_depmod #15 _start -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 1

[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 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 23 Feb '15

23 Feb '15

https://bugzilla.redhat.com/show_bug.cgi?id=634736 --- Comment #44 from Laine Stump <laine(a)redhat.com> --- After all these years of asking for the default of bridge filtering to be "disabled" and the change being refused by the kernel maintainers, now the filtering has been moved into a separate module that isn't loaded (by default) when the bridge module is loaded, effectively making the default "disabled". Yay! I *think* this is in the kernel as of 3.17 (It definitely is in kernel 3.18.7-200.fc21, and appears to be in git prior to the tag "v3.17-rc4") So again the problem has disappeared for our case, so we're happy, but the general problem (as in the latest version of this bug's summary) is still there. What is the proper action for this BZ then? Do we leave it around (knowing that, based on the experience up to now, the general problem will likely never be fixed), close it as WONTFIX, or close it with one or another of the "resolved" reasons, since our particular problem has been fixed by the addition of the new module? -- 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=RAeNfi7MWs&a=cc_unsubscribe

1 0

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 22 Feb '15

22 Feb '15

https://bugzilla.redhat.com/show_bug.cgi?id=634736 Scott Shambarger <scott-redhat(a)shambarger.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scott-redhat(a)shambarger.net --- Comment #43 from Scott Shambarger <scott-redhat(a)shambarger.net> --- Just noticed the boot message: bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. The new module appears to export the bridge sysctl values, but the udev rule in /lib/udev/rules.d/99-bridge.rules still refers to the bridge module (not the br_netfilter module), and so the bridge netfilter values after loading br_netfilter are: net.bridge.bridge-nf-call-arptables = 1 net.bridge.bridge-nf-call-ip6tables = 1 net.bridge.bridge-nf-call-iptables = 1 Granted, if you load br_netfilter explicitly, you probably want to use it, but then /usr/sysctl.d/50-bridge.conf should probably be removed as it is no longer needed to disable bridge netfilter (by default) anymore. -- 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=VYBg4gc3n0&a=cc_unsubscribe

1 0

[kmod] Rebuilt for Fedora 23 Change
by Till Maas 21 Feb '15

21 Feb '15

commit cd00fbfabb325ee46ce25f4615eb3de6b3a924b5 Author: Till Maas <opensource(a)till.name> Date: Sat Feb 21 22:26:42 2015 +0100 Rebuilt for Fedora 23 Change https://fedoraproject.org/wiki/Changes/Harden_all_packages_with_position-in… kmod.spec | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) --- diff --git a/kmod.spec b/kmod.spec index 156cbd6..aef964f 100644 --- a/kmod.spec +++ b/kmod.spec @@ -1,6 +1,6 @@ Name: kmod Version: 19 -Release: 1%{?dist} +Release: 2%{?dist} Summary: Linux kernel module management utilities Group: System Environment/Kernel @@ -111,6 +111,10 @@ install -m 755 %{SOURCE1} $RPM_BUILD_ROOT%{_sbindir}/weak-modules %{_libdir}/libkmod.so %changelog +* Sat Feb 21 2015 Till Maas <opensource(a)till.name> - 19-2 +- Rebuilt for Fedora 23 Change + https://fedoraproject.org/wiki/Changes/Harden_all_packages_with_position-in… + * Sun Nov 16 2014 Josh Boyer <jwboyer(a)fedoraproject.org> - 19-1 - Update to version 19

1 0

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 16 Feb '15

16 Feb '15

https://bugzilla.redhat.com/show_bug.cgi?id=634736 --- Comment #42 from Edgar Hoch <edgar.hoch(a)ims.uni-stuttgart.de> --- I agree that forking "sysctl" for each loaded module induce much unnecessary overhead. So we need a better solution. I think it may be too complicated for an ordinary user - and for an ordinary administrator too - to write udev rules when he just want to change the value of a parameter. udev rules are much more complex than a single parameter assignment. I think that there should be a tool with a simple user interface like sysctl, which users and admins can use to read, set and change parameters of the system. It may generate udev rule files instead of sysctl config files, that would be ok. It should have at least a cli, but some gui (maybe combined with other configuration tools) would be nice too. The tool should support temporary changes of the parameters (to the running system, lost after reboot) and permanant changes (changes files in /etc/...) - preferred by the same tool. There should also be some reasonable defaults for frequent use cases. I think bridges with a vm (kvm, libvirt) with external ip addresses (not nat) is a typical case. virsh is no help for this case (see bug #1134569). -- 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=zXYeIdLzDK&a=cc_unsubscribe

1 0

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 16 Feb '15

16 Feb '15

1 0

[Bug 634736] sysctl.conf / sysctl.conf.d settings not read when modules are loaded
by Red Hat Bugzilla 16 Feb '15

16 Feb '15

https://bugzilla.redhat.com/show_bug.cgi?id=634736 --- Comment #40 from Lennart Poettering <lpoetter(a)redhat.com> --- To summarize my stance on this: - doesn't belong in systemd.rpm, if at all it should be in bridge-utils or so - really bad idea in general, you cannot win, there are so many kmods, so it should not happen at all. And even if you added this for every single kmod that exports a sysctl, you'd slow down the boot tremendously, since sysctl needs to be forked off for every single one of them. - fedora-specific "solutions" to this are a bad idea anyway, let's make everybody use the same logic here, and that should be udev rules. -- 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 16 Feb '15

16 Feb '15

https://bugzilla.redhat.com/show_bug.cgi?id=634736 --- Comment #39 from Lennart Poettering <lpoetter(a)redhat.com> --- Hmm, I really disagree with this fix. I am absolutely sure we shouldn't add similar rules for any kmod that comes along. People really should find a different way for this: write their own udev rules or whatever they like, but doing this for ever single kmod in systemd is not an option. I will now remove this patch from f22. This really has no place in the systemd RPM. If you really want to keep this, move it to the bridge-utils or so, but honestly: it's really time to forget sysctls for modules, it will not work, and people shouldn't try. -- 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 February 2015