[opensuse-kernel] Kernel Update (broken) "martian Source" 12.3
Hello, what is changed (broken ?) with the last kernel update? Yesterday I installed the last kernel Update (3.7.10-1.11) now I have a full messages log file with techz kernel: [ 2632.076419] IPv4: martian source 192.168.100.255 from 192.168.100.100, on dev eth1 techz kernel: [ 2632.076425] ll header: 00000000: ff ff ff ff ff ff 70 71 bc e2 cf fb 08 00 ......pq...... With kernel 3.7.10-1.4 this Problem don't exist? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
В Thu, 30 May 2013 10:57:59 +0200 Günther J. Niederwimmer <gjn@gjn.priv.at> пишет:
Hello,
what is changed (broken ?) with the last kernel update?
Yesterday I installed the last kernel Update (3.7.10-1.11) now I have a full messages log file with
techz kernel: [ 2632.076419] IPv4: martian source 192.168.100.255 from 192.168.100.100, on dev eth1 techz kernel: [ 2632.076425] ll header: 00000000: ff ff ff ff ff ff 70 71 bc e2 cf fb 08 00 ......pq......
With kernel 3.7.10-1.4 this Problem don't exist?
Could you compare value of log_martians on both kernels? I have on 3.7.10-1.4: bor@opensuse:~> sudo /sbin/sysctl -a | fgrep .log_martians net.ipv4.conf.all.log_martians = 0 net.ipv4.conf.default.log_martians = 0 net.ipv4.conf.eth0.log_martians = 0 net.ipv4.conf.lo.log_martians = 0 net.ipv4.conf.wlan0.log_martians = 0 bor@opensuse:~> -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Hello, Am Donnerstag, 30. Mai 2013, 14:59:04 schrieb Andrey Borzenkov:
В Thu, 30 May 2013 10:57:59 +0200
Günther J. Niederwimmer <gjn@gjn.priv.at> пишет:
Hello,
what is changed (broken ?) with the last kernel update?
Yesterday I installed the last kernel Update (3.7.10-1.11) now I have a full messages log file with
techz kernel: [ 2632.076419] IPv4: martian source 192.168.100.255 from 192.168.100.100, on dev eth1 techz kernel: [ 2632.076425] ll header: 00000000: ff ff ff ff ff ff 70 71 bc e2 cf fb 08 00 ......pq......
With kernel 3.7.10-1.4 this Problem don't exist?
Could you compare value of log_martians on both kernels? I have on 3.7.10-1.4:
bor@opensuse:~> sudo /sbin/sysctl -a | fgrep .log_martians net.ipv4.conf.all.log_martians = 0 net.ipv4.conf.default.log_martians = 0 net.ipv4.conf.eth0.log_martians = 0 net.ipv4.conf.lo.log_martians = 0 net.ipv4.conf.wlan0.log_martians = 0 bor@opensuse:~>
On my System with the Kernel 3.7.10-1.11 I have now this sudo /sbin/sysctl -a | fgrep .log_martians net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1 net.ipv4.conf.eth0.log_martians = 1 net.ipv4.conf.eth1.log_martians = 1 net.ipv4.conf.lo.log_martians = 1 net.ipv4.conf.wlan0.log_martians = 1 For the 3.7.10-1.4 I have to restart ;) -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2013-05-30 at 13:16 +0200, Günther J. Niederwimmer wrote:
Could you compare value of log_martians on both kernels? I have on 3.7.10-1.4:
For the 3.7.10-1.4 I have to restart ;)
I get the same results on both: eleanor3:/home/cer # /sbin/sysctl -a | fgrep .log_martians net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1 net.ipv4.conf.eth0.log_martians = 1 net.ipv4.conf.lo.log_martians = 1 eleanor3:/home/cer # uname -a Linux eleanor3.valinor 3.7.10-1.4-desktop #1 SMP PREEMPT Fri Apr 19 12:06:34 UTC 2013 (8ef74f8) x86_64 x86_64 x86_64 GNU/Linux eleanor3:/home/cer # exit cer@eleanor3:~> logout Connection to 192.168.74.127 closed. cer@Telcontar:~> ssh root@192.168.74.127 Password: Last login: Thu May 30 04:18:11 2013 Have a lot of fun... eleanor3:~ # sysctl -a | fgrep .log_martians net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1 net.ipv4.conf.eth0.log_martians = 1 net.ipv4.conf.lo.log_martians = 1 eleanor3:~ # uname -a Linux eleanor3.valinor 3.7.10-1.11-desktop #1 SMP PREEMPT Thu May 16 20:27:27 UTC 2013 (adf31bb) x86_64 x86_64 x86_64 GNU/Linux eleanor3:~ # - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlGnPVgACgkQtTMYHG2NR9XfQACfXqeZHyA2TxB2QaBw/HAI0LKx OMwAn2CHPpBrJbi/P77trRZixiUffpzd =x4Li -----END PGP SIGNATURE-----
Hello, Am Donnerstag, 30. Mai 2013, 13:51:45 schrieb Carlos E. R.:
On Thursday, 2013-05-30 at 13:16 +0200, Günther J. Niederwimmer wrote:
Could you compare value of log_martians on both kernels? I have on
3.7.10-1.4: For the 3.7.10-1.4 I have to restart ;)
I get the same results on both:
eleanor3:/home/cer # /sbin/sysctl -a | fgrep .log_martians net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1 net.ipv4.conf.eth0.log_martians = 1 net.ipv4.conf.lo.log_martians = 1 eleanor3:/home/cer # uname -a Linux eleanor3.valinor 3.7.10-1.4-desktop #1 SMP PREEMPT Fri Apr 19 12:06:34 UTC 2013 (8ef74f8) x86_64 x86_64 x86_64 GNU/Linux eleanor3:/home/cer # exit cer@eleanor3:~> logout Connection to 192.168.74.127 closed. cer@Telcontar:~> ssh root@192.168.74.127 Password: Last login: Thu May 30 04:18:11 2013 Have a lot of fun... eleanor3:~ # sysctl -a | fgrep .log_martians net.ipv4.conf.all.log_martians = 1 net.ipv4.conf.default.log_martians = 1 net.ipv4.conf.eth0.log_martians = 1 net.ipv4.conf.lo.log_martians = 1 eleanor3:~ # uname -a Linux eleanor3.valinor 3.7.10-1.11-desktop #1 SMP PREEMPT Thu May 16 20:27:27 UTC 2013 (adf31bb) x86_64 x86_64 x86_64 GNU/Linux eleanor3:~ #
After restart with kernel 3.7.10-1.4 I have also the same result and also the Logs? :(. After Zypper Log search, the only Update I found are mkinitrd and YaST- Installation I mean. But 3 days before, I don't have this martian source in the log (?) This is Bad..... -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Thursday 30 of May 2013 14:19EN, Günther J. Niederwimmer wrote:
After restart with kernel 3.7.10-1.4 I have also the same result and also the Logs? :(.
After Zypper Log search, the only Update I found are mkinitrd and YaST- Installation I mean.
But 3 days before, I don't have this martian source in the log (?)
Can you check "grep -r log_martians /etc/sysctl.*" ? If there is a file setting it to 1, you can check what package does it belong to, check its mtime and compare the timestamp with entries in /var/log/zypp/history Michal Kubeček -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
В Thu, 30 May 2013 14:19:15 +0200 Günther J. Niederwimmer <gjn@gjn.priv.at> пишет:
After restart with kernel 3.7.10-1.4 I have also the same result and also the Logs? :(.
log_martians are set by default by SuSEfierwall2 service (unless explicitly disabled). Did you have firewall active before? If it was disabled before installing updates and became enabled after it is a bug. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
В Thu, 30 May 2013 10:57:59 +0200 Günther J. Niederwimmer <gjn@gjn.priv.at> пишет:
Hello,
what is changed (broken ?) with the last kernel update?
Yesterday I installed the last kernel Update (3.7.10-1.11) now I have a full messages log file with
techz kernel: [ 2632.076419] IPv4: martian source 192.168.100.255 from 192.168.100.100, on dev eth1 techz kernel: [ 2632.076425] ll header: 00000000: ff ff ff ff ff ff 70 71 bc e2 cf fb 08 00 ......pq......
Irrespectively of why it is suddenly logged - this indicates possible network misconfiguration. Could you show "ifconfig -a" output? -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On 05/30/2013 10:57 AM, Günther J. Niederwimmer wrote:
Hello,
what is changed (broken ?) with the last kernel update?
Yesterday I installed the last kernel Update (3.7.10-1.11) now I have a full messages log file with
techz kernel: [ 2632.076419] IPv4: martian source 192.168.100.255 from 192.168.100.100, on dev eth1 techz kernel: [ 2632.076425] ll header: 00000000: ff ff ff ff ff ff 70 71 bc e2 cf fb 08 00 ......pq......
With kernel 3.7.10-1.4 this Problem don't exist?
It is unlikely something to be broken in the networking stack. Better question to ask is who is 192.168.100.100 and why it started telling about itself to be 192.168.100.255... Hm? -- js suse labs -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Thursday 30 of May 2013 15:43EN, Jiri Slaby wrote:
On 05/30/2013 10:57 AM, Günther J. Niederwimmer wrote:
techz kernel: [ 2632.076419] IPv4: martian source 192.168.100.255 from 192.168.100.100, on dev eth1 techz kernel: [ 2632.076425] ll header: 00000000: ff ff ff ff ff ff 70 71 bc e2 cf fb 08 00 ......pq......
It is unlikely something to be broken in the networking stack. Better question to ask is who is 192.168.100.100 and why it started telling about itself to be 192.168.100.255... Hm?
I may have overlooked something but from the source it looks like this might just mean that a packet from 192.168.100.100 to 192.168.100.255 has been received on an interface RP filter considers wrong. Output of "ip addr show", "ip route show" and "ip neigh show" would definitely tell us more. Michal Kubeček -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Hello Am Donnerstag, 30. Mai 2013, 16:00:58 schrieb Michal Kubeček:
On Thursday 30 of May 2013 15:43EN, Jiri Slaby wrote:
On 05/30/2013 10:57 AM, Günther J. Niederwimmer wrote:
techz kernel: [ 2632.076419] IPv4: martian source 192.168.100.255 from 192.168.100.100, on dev eth1 techz kernel: [ 2632.076425] ll header: 00000000: ff ff ff ff ff ff 70 71 bc e2 cf fb 08 00 ......pq......
It is unlikely something to be broken in the networking stack. Better question to ask is who is 192.168.100.100 and why it started telling about itself to be 192.168.100.255... Hm?
I may have overlooked something but from the source it looks like this might just mean that a packet from 192.168.100.100 to 192.168.100.255 has been received on an interface RP filter considers wrong.
Output of "ip addr show", "ip route show" and "ip neigh show" would definitely tell us more.
OK. ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 70:71:bc:e2:cf:fb brd ff:ff:ff:ff:ff:ff inet 192.168.100.100/24 brd 192.168.100.255 scope global eth0 inet6 2001:15c0:65ff:868c:bd3d:4977:e126:5f91/64 scope global temporary dynamic valid_lft 585359sec preferred_lft 66359sec inet6 2001:15c0:65ff:868c:7271:bcff:fee2:cffb/64 scope global dynamic valid_lft 2591515sec preferred_lft 604315sec inet6 fe80::7271:bcff:fee2:cffb/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1480 qdisc pfifo_fast state UP qlen 1000 link/ether 70:71:bc:e2:cf:fd brd ff:ff:ff:ff:ff:ff inet6 2001:15c0:65ff:868c:a46a:6dcc:3c76:cb42/64 scope global temporary dynamic valid_lft 585359sec preferred_lft 66359sec inet6 2001:15c0:65ff:868c:7271:bcff:fee2:cffd/64 scope global dynamic valid_lft 2591515sec preferred_lft 604315sec inet6 2001:15c0:65ff:868c::64/64 scope global valid_lft forever preferred_lft forever inet6 fe80::7271:bcff:fee2:cffd/64 scope link valid_lft forever preferred_lft forever 4: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 6c:62:6d:25:57:b9 brd ff:ff:ff:ff:ff:ff ip route show default via 192.168.100.210 dev eth0 127.0.0.0/8 dev lo scope link 169.254.0.0/16 dev eth0 scope link ip -6 route show 2001:15c0:65ff:868c::/64 dev eth1 proto kernel metric 256 2001:15c0:65ff:868c::/64 dev eth0 proto kernel metric 256 expires 2591820sec fe80::/64 dev eth0 proto kernel metric 256 fe80::/64 dev eth1 proto kernel metric 256 default via 2001:15c0:65ff:868c::1 dev eth1 metric 1024 default via fe80::215:17ff:fe13:b8a7 dev eth1 proto ra metric 1024 expires 1620sec default via fe80::215:17ff:fe13:b8a7 dev eth0 proto ra metric 1024 expires 1620sec ip neigh show fe80::215:17ff:fe13:b8a7 dev eth1 lladdr 00:15:17:13:b8:a7 router STALE fe80::215:17ff:fe13:b8a7 dev eth0 lladdr 00:15:17:13:b8:a7 router STALE 2001:15c0:65ff:868c::1 dev eth1 lladdr 00:1b:21:6a:7c:4f router STALE 192.168.100.220 dev eth0 lladdr 00:15:17:13:b8:a6 STALE 192.168.100.210 dev eth0 lladdr 00:1c:c0:a3:9f:4b STALE 192.168.100.223 dev eth0 lladdr 00:16:3e:68:8e:bf REACHABLE -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Thu, May 30, 2013 at 10:38:10PM +0200, Günther J. Niederwimmer wrote:
Am Donnerstag, 30. Mai 2013, 16:00:58 schrieb Michal Kubeček:
On Thursday 30 of May 2013 15:43EN, Jiri Slaby wrote:
On 05/30/2013 10:57 AM, Günther J. Niederwimmer wrote:
techz kernel: [ 2632.076419] IPv4: martian source 192.168.100.255 from 192.168.100.100, on dev eth1 techz kernel: [ 2632.076425] ll header: 00000000: ff ff ff ff ff ff 70 71 bc e2 cf fb 08 00 ......pq......
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 70:71:bc:e2:cf:fb brd ff:ff:ff:ff:ff:ff inet 192.168.100.100/24 brd 192.168.100.255 scope global eth0 inet6 2001:15c0:65ff:868c:bd3d:4977:e126:5f91/64 scope global temporary dynamic valid_lft 585359sec preferred_lft 66359sec inet6 2001:15c0:65ff:868c:7271:bcff:fee2:cffb/64 scope global dynamic valid_lft 2591515sec preferred_lft 604315sec inet6 fe80::7271:bcff:fee2:cffb/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1480 qdisc pfifo_fast state UP qlen 1000 link/ether 70:71:bc:e2:cf:fd brd ff:ff:ff:ff:ff:ff inet6 2001:15c0:65ff:868c:a46a:6dcc:3c76:cb42/64 scope global temporary dynamic valid_lft 585359sec preferred_lft 66359sec inet6 2001:15c0:65ff:868c:7271:bcff:fee2:cffd/64 scope global dynamic valid_lft 2591515sec preferred_lft 604315sec inet6 2001:15c0:65ff:868c::64/64 scope global valid_lft forever preferred_lft forever inet6 fe80::7271:bcff:fee2:cffd/64 scope link valid_lft forever preferred_lft forever
So the problem is that a (broadcast) packet from you sent to eth0 was received on eth1 which RP filter doesn't like. I dare to guess that you connected both eth0 and eth1 to the same ethernet segment. It is is not necessarily wrong and there are legitimate reasons to do that (but perhaps bonding might be more suitable solution). Anyway, in such case (as in many others), RP filter should be either disabled or at least set to loose mode, i.e. rp_filter sysctl should be set to 0 or 2. Unfortunately the default in OpenSuSE is 1 (strict mode). Michal Kubeček -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Am Donnerstag, 30. Mai 2013, 23:10:23 schrieb Michal Kubecek:
On Thu, May 30, 2013 at 10:38:10PM +0200, Günther J. Niederwimmer wrote:
Am Donnerstag, 30. Mai 2013, 16:00:58 schrieb Michal Kubeček:
On Thursday 30 of May 2013 15:43EN, Jiri Slaby wrote:
On 05/30/2013 10:57 AM, Günther J. Niederwimmer wrote:
techz kernel: [ 2632.076419] IPv4: martian source 192.168.100.255 from 192.168.100.100, on dev eth1 techz kernel: [ 2632.076425] ll header: 00000000: ff ff ff ff ff ff 70 71 bc e2 cf fb 08 00 ......pq......
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 70:71:bc:e2:cf:fb brd ff:ff:ff:ff:ff:ff inet 192.168.100.100/24 brd 192.168.100.255 scope global eth0 inet6 2001:15c0:65ff:868c:bd3d:4977:e126:5f91/64 scope global temporary
dynamic
valid_lft 585359sec preferred_lft 66359sec
inet6 2001:15c0:65ff:868c:7271:bcff:fee2:cffb/64 scope global dynamic
valid_lft 2591515sec preferred_lft 604315sec
inet6 fe80::7271:bcff:fee2:cffb/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1480 qdisc pfifo_fast state UP qlen 1000
link/ether 70:71:bc:e2:cf:fd brd ff:ff:ff:ff:ff:ff inet6 2001:15c0:65ff:868c:a46a:6dcc:3c76:cb42/64 scope global temporary
dynamic
valid_lft 585359sec preferred_lft 66359sec
inet6 2001:15c0:65ff:868c:7271:bcff:fee2:cffd/64 scope global dynamic
valid_lft 2591515sec preferred_lft 604315sec
inet6 2001:15c0:65ff:868c::64/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::7271:bcff:fee2:cffd/64 scope link
valid_lft forever preferred_lft forever
So the problem is that a (broadcast) packet from you sent to eth0 was received on eth1 which RP filter doesn't like. I dare to guess that you connected both eth0 and eth1 to the same ethernet segment. It is is not necessarily wrong and there are legitimate reasons to do that (but perhaps bonding might be more suitable solution). Anyway, in such case (as in many others), RP filter should be either disabled or at least set to loose mode, i.e. rp_filter sysctl should be set to 0 or 2. Unfortunately the default in OpenSuSE is 1 (strict mode).
OK, thak's I search in google ;) This is for me, a mystery Situation. I make yesterday a Test, I installed the system new only with one NIC (no seperate IPv6), and now the "martian_source" Log is gone again (?). Have any a link for Information or tests for this situation, I have a XEN SLES Test Installation with the same Problem, full running logs on all Instances :-(. I don't remember is this starting with a kernel update or my IPv6 config? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Sat, Jun 01, 2013 at 02:45:02PM +0200, Günther J. Niederwimmer wrote:
I make yesterday a Test, I installed the system new only with one NIC (no seperate IPv6), and now the "martian_source" Log is gone again (?).
This makes sense - as I explained in previous mail, in your case the "martian" was a a packet sent by you to one interface and received on another, most likely connected to the same ethernet segment. If you have only one interface, this cannot happen. Michal Kubeček -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
Hello Michal, Am Samstag, 1. Juni 2013, 15:33:47 schrieb Michal Kubecek:
On Sat, Jun 01, 2013 at 02:45:02PM +0200, Günther J. Niederwimmer wrote:
I make yesterday a Test, I installed the system new only with one NIC (no seperate IPv6), and now the "martian_source" Log is gone again (?).
This makes sense - as I explained in previous mail, in your case the "martian" was a a packet sent by you to one interface and received on another, most likely connected to the same ethernet segment. If you have only one interface, this cannot happen.
No I have two, I have configured the first for internal IPv4 and the second should be a external IPv6 only Interface. But I mean I do wrong or i can't understand this Situation (?). In my Xen Situation I have three Bridges 1 x IPv4 external 1x IPv4 internal and a external IPv6 For me I mean, it is a Problem to separating clear IPv6 and IPv4? -- mit freundlichen Grüßen / best Regards, Günther J. Niederwimmer -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
On Sat, Jun 01, 2013 at 04:45:09PM +0200, Günther J. Niederwimmer wrote:
For me I mean, it is a Problem to separating clear IPv6 and IPv4?
I don't see a reason for it but it (as such) is not a problem. But if you want to connect two interfaces into the same ethernet segment, you need to turn of the RP filter (or at least switch it to loose mode). Michal Kubeček -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
participants (6)
-
Andrey Borzenkov -
Carlos E. R. -
Günther J. Niederwimmer -
Jiri Slaby -
Michal Kubecek -
Michal Kubeček