* [xtables-addons] Oops in SYSRQ, BUG: unable to handle kernel paging request at ffffffffa01a90e0
@ 2012-01-20 16:48 Marcin Mirosław
2012-01-20 17:14 ` Jan Engelhardt
2012-08-23 13:23 ` Jan Engelhardt
0 siblings, 2 replies; 5+ messages in thread
From: Marcin Mirosław @ 2012-01-20 16:48 UTC (permalink / raw)
To: netfilter
Hi again!
I've found bug in xt_SYSRQ (probably), when i add rule with sysrq,
remove rule, unload module then add rule i'm getting Oops. Please look
at this:
# grep xt /proc/modules
# iptables -A INPUT -s 195.242.255.127 -p udp --dport 29999 -j SYSRQ
# echo -n "xxx" > /sys/module/xt_SYSRQ/parameters/password
# iptables -F
# rmmod xt_SYSRQ
# iptables -A INPUT -s 195.242.255.127 -p udp --dport 29999 -j SYSRQ
Message from syslogd@meteor at Jan 20 17:41:12 ...
kernel:[ 159.986759] Oops: 0000 [#1] SMP
Message from syslogd@meteor at Jan 20 17:41:12 ...
kernel:[ 159.989504] Stack:
Message from syslogd@meteor at Jan 20 17:41:12 ...
kernel:[ 159.989504] Call Trace:
Message from syslogd@meteor at Jan 20 17:41:12 ...
kernel:[ 159.989504] Code: 4d 8b 24 24 4d 39 e5 74 71 49 8d 7c 24 10
48 89 de e8 b4 0b f2 ff 85 c0 75 e6 45 38 74 24 2d 75 d9 49 8b 44 24 58
48 85 c0 74 1e
Message from syslogd@meteor at Jan 20 17:41:12 ...
kernel:[ 159.989504] CR2: ffffffffa01a90e0
Here is all Oops:
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.982114] BUG:
unable to handle kernel paging request at ffffffffa01a90e0
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.983757] IP:
[<ffffffff812ae571>] xt_find_target+0xa1/0x120
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.984688] PGD
132d067 PUD 1333063 PMD 1d8a6063 PTE 0
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.986759] Oops:
0000 [#1] SMP
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.987873] CPU 0
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.988131] Modules
linked in: sha1_generic compat_xtables ip6_tables zram(C) iptable_filter
ip_tables sit tunnel4 xfs exportfs dm_mod ipv6 sr_mod 8139too evdev
cdrom 8139cp [last unloaded: xt_SYSRQ]
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504]
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] Pid:
2388, comm: iptables Tainted: G C 3.1.8-hardened #5 Xen HVM domU
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] RIP:
0010:[<ffffffff812ae571>] [<ffffffff812ae571>] xt_find_target+0xa1/0x120
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] RSP:
0018:ffff880016f01b98 EFLAGS: 00010282
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] RAX:
ffffffffa01a90e0 RBX: ffff880016f090a2 RCX: ffff880016f090a0
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] RDX:
0000000000000000 RSI: ffff880016f090a8 RDI: ffff880016d82b96
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] RBP:
ffff880016f01be8 R08: 0000000000000010 R09: ffff880016f09260
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] R10:
0000000000000000 R11: 0000000000000010 R12: ffff880016d82b80
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] R13:
ffff88001e9e8910 R14: 0000000000000001 R15: 00000000fffffffe
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] FS:
0000039baee6d700(0000) GS:ffff88001fc00000(0000) knlGS:0000000000000000
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] CS: 0010
DS: 0000 ES: 0000 CR0: 0000000080050033
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] CR2:
ffffffffa01a90e0 CR3: 0000000001325000 CR4: 00000000000006b0
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] DR0:
0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] DR3:
0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] Process
iptables (pid: 2388, threadinfo ffff88001e32ce30, task ffff88001e32ca40)
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] Stack:
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504]
ffff880016f01c28 0200000000000018 00000000000000e0 ffff88001e9e88e0
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504]
ffff88001f5745c0 0000000000000002 ffff880016f090a2 0000000000000001
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504]
0000000000000001 ffff88001e159c60 ffff880016f01c18 ffffffff812af499
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] Call Trace:
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504]
[<ffffffff812af499>] xt_request_find_target+0x29/0x80
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504]
[<ffffffffa0151389>] translate_table+0x389/0x660 [ip_tables]
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504]
[<ffffffffa0152e05>] do_ipt_set_ctl+0x1f5/0x2a0 [ip_tables]
2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504]
[<ffffffff812ad456>] nf_sockopt+0x66/0xc0
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504]
[<ffffffff812ad4ec>] nf_setsockopt+0x1c/0x30
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504]
[<ffffffff812bee54>] ip_setsockopt+0x94/0xb0
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504]
[<ffffffff812dc105>] raw_setsockopt+0x25/0x50
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504]
[<ffffffff8127347c>] sock_common_setsockopt+0x1c/0x30
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504]
[<ffffffff81272357>] sys_setsockopt+0x87/0xf0
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504]
[<ffffffff81316f7b>] system_call_fastpath+0x18/0x1d
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504]
[<ffffffff813169f5>] ? page_fault+0x35/0x40
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504]
[<ffffffff813167b3>] ? retint_swapgs+0xc/0x12
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504] Code: 4d
8b 24 24 4d 39 e5 74 71 49 8d 7c 24 10 48 89 de e8 b4 0b f2 ff 85 c0 75
e6 45 38 74 24 2d 75 d9 49 8b 44 24 58 48 85 c0 74 1e
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504] RIP
[<ffffffff812ae571>] xt_find_target+0xa1/0x120
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504] RSP
<ffff880016f01b98>
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504] CR2:
ffffffffa01a90e0
2012-01-20T17:41:12.286824+01:00 meteor kernel: [ 159.989504] ---[ end
trace 5347f098273ef2a7 ]---
$ uname -r
3.1.8-hardened
# iptables -V
iptables v1.4.12.1
Regards.
Marcin
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xtables-addons] Oops in SYSRQ, BUG: unable to handle kernel paging request at ffffffffa01a90e0
2012-01-20 16:48 [xtables-addons] Oops in SYSRQ, BUG: unable to handle kernel paging request at ffffffffa01a90e0 Marcin Mirosław
@ 2012-01-20 17:14 ` Jan Engelhardt
2012-01-20 18:59 ` Marcin Mirosław
2012-08-23 13:23 ` Jan Engelhardt
1 sibling, 1 reply; 5+ messages in thread
From: Jan Engelhardt @ 2012-01-20 17:14 UTC (permalink / raw)
To: Marcin Mirosław; +Cc: netfilter
On Friday 2012-01-20 17:48, Marcin Mirosław wrote:
>Hi again!
>I've found bug in xt_SYSRQ (probably), when i add rule with sysrq,
>remove rule, unload module then add rule i'm getting Oops. Please look
>at this:
>
>2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.988131] Modules
>linked in: sha1_generic compat_xtables ip6_tables zram(C) iptable_filter
>ip_tables sit tunnel4 xfs exportfs dm_mod ipv6 sr_mod 8139too evdev
>cdrom 8139cp [last unloaded: xt_SYSRQ]
>2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504]
>2012-01-20T17:41:12.276820+01:00 meteor kernel: [ 159.989504] Pid:
>2388, comm: iptables Tainted: G C 3.1.8-hardened #5 Xen HVM domU
You have a crappy module (indicated by the "C") loaded, and since it's
zram, I don't know what effects that could have w.r.t. memory corruption.
Is this reproducible without zram?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xtables-addons] Oops in SYSRQ, BUG: unable to handle kernel paging request at ffffffffa01a90e0
2012-01-20 17:14 ` Jan Engelhardt
@ 2012-01-20 18:59 ` Marcin Mirosław
0 siblings, 0 replies; 5+ messages in thread
From: Marcin Mirosław @ 2012-01-20 18:59 UTC (permalink / raw)
To: Jan Engelhardt; +Cc: netfilter
W dniu 2012-01-20 18:14, Jan Engelhardt napisał(a):
> You have a crappy module (indicated by the "C") loaded, and since
> it's
> zram, I don't know what effects that could have w.r.t. memory
> corruption.
> Is this reproducible without zram?
Hi Jan,
without zram/zcache oops still appears, new log:
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.235485] BUG:
unable to handle kernel paging request at ffffffffa01d80e
0
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.237586] IP:
[<ffffffff812a9451>] xt_find_target+0xa1/0x120
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.238616] PGD
1328067 PUD 132e063 PMD 1e29a063 PTE 0
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.240035] Oops:
0000 [#1] SMP
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.241398] CPU 0
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.241737] Modules
linked in: sit tunnel4 xt_TCPMSS ipt_REJECT xt_multipo
rt xt_set xt_TARPIT ip_set_hash_ip ip_set_hash_net sha1_generic
compat_xtables nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_rt xt_st
ate xt_NOTRACK ip_set iptable_raw ip6table_mangle iptable_mangle
iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_
ipv4 ip6table_filter ip6_tables iptable_filter ip_tables xfs exportfs
dm_mod ipv6 8139too evdev sr_mod cdrom 8139cp [last unl
oaded: xt_SYSRQ]
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436]
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] Pid:
4895, comm: iptables Not tainted 3.1.8-hardened #6 Xen HV
M domU
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] RIP:
0010:[<ffffffff812a9451>] [<ffffffff812a9451>] xt_find_t
arget+0xa1/0x120
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] RSP:
0018:ffff880017f53c18 EFLAGS: 00010282
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] RAX:
ffffffffa01d80e0 RBX: ffff880017e59382 RCX: ffff880017e59
380
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] RDX:
0000000000000000 RSI: ffff880017e59388 RDI: ffff88001dcdf
e96
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] RBP:
ffff880017f53c68 R08: 0000000000000010 R09: ffff880017e59
758
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] R10:
0000000000000000 R11: 0000000000000010 R12: ffff88001dcdf
e80
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] R13:
ffff88001ea75910 R14: 0000000000000001 R15: 00000000fffff
ffe
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] FS:
000002c51ebe1700(0000) GS:ffff88001fc00000(0000) knlGS:00
00000000000000
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] CS:
0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] CR2:
ffffffffa01d80e0 CR3: 0000000001320000 CR4: 0000000000000
6b0
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] DR0:
0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] DR3:
0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] Process
iptables (pid: 4895, threadinfo ffff88001ebf6270, task ffff88001ebf5e80)
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436] Stack:
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436]
ffff880017f53c28 02a7b27e0ae1476c 00000000000000e0 ffff88001ea758e0
2012-01-20T18:54:48.808195+01:00 meteor kernel: [ 115.243436]
ffff880017e59260 0000000000000002 ffff880017e59382 0000000000000001
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
0000000000000001 ffff88001d68c600 ffff880017f53c98 ffffffff812aa379
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] Call
Trace:
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff812aa379>] xt_request_find_target+0x29/0x80
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffffa0140389>] translate_table+0x389/0x660 [ip_tables]
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffffa0141e05>] do_ipt_set_ctl+0x1f5/0x2a0 [ip_tables]
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff812a8336>] nf_sockopt+0x66/0xc0
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff812a83cc>] nf_setsockopt+0x1c/0x30
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff812b9d34>] ip_setsockopt+0x94/0xb0
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff812d6fe5>] raw_setsockopt+0x25/0x50
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff8126e35c>] sock_common_setsockopt+0x1c/0x30
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff8126d237>] sys_setsockopt+0x87/0xf0
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436]
[<ffffffff81311e7b>] system_call_fastpath+0x18/0x1d
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] Code: 4d
8b 24 24 4d 39 e5 74 71 49 8d 7c 24 10 48 89 de e8 d4 5c f2 ff 85 c0 75
e6 45 38 74 24 2d 75 d9 49 8b 44 24 58 48 85 c0 74 1e
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] RIP
[<ffffffff812a9451>] xt_find_target+0xa1/0x120
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] RSP
<ffff880017f53c18>
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] CR2:
ffffffffa01d80e0
2012-01-20T18:54:48.818199+01:00 meteor kernel: [ 115.243436] ---[ end
trace cfa32e0ddddcd297 ]---
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xtables-addons] Oops in SYSRQ, BUG: unable to handle kernel paging request at ffffffffa01a90e0
2012-01-20 16:48 [xtables-addons] Oops in SYSRQ, BUG: unable to handle kernel paging request at ffffffffa01a90e0 Marcin Mirosław
2012-01-20 17:14 ` Jan Engelhardt
@ 2012-08-23 13:23 ` Jan Engelhardt
2012-09-18 11:20 ` Marcin Mirosław
1 sibling, 1 reply; 5+ messages in thread
From: Jan Engelhardt @ 2012-08-23 13:23 UTC (permalink / raw)
To: Marcin Mirosław; +Cc: netfilter
On Friday 2012-01-20 17:48, Marcin Mirosław wrote:
>Hi again!
>I've found bug in xt_SYSRQ (probably), when i add rule with sysrq,
>remove rule, unload module then add rule i'm getting Oops. Please look
>at this:
Maybe fixed with commit
commit cb8050172ae1d893f58c1aa57de975f9932dace6 (v1.44~4)
Author: Jan Engelhardt <jengelh@inai.de>
Date: Wed Jul 11 01:42:39 2012 +0200
SYSRQ: fix double target initialization at module load
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [xtables-addons] Oops in SYSRQ, BUG: unable to handle kernel paging request at ffffffffa01a90e0
2012-08-23 13:23 ` Jan Engelhardt
@ 2012-09-18 11:20 ` Marcin Mirosław
0 siblings, 0 replies; 5+ messages in thread
From: Marcin Mirosław @ 2012-09-18 11:20 UTC (permalink / raw)
To: Jan Engelhardt; +Cc: netfilter
W dniu 23.08.2012 15:23, Jan Engelhardt pisze:
> On Friday 2012-01-20 17:48, Marcin Mirosław wrote:
>
>> Hi again!
>> I've found bug in xt_SYSRQ (probably), when i add rule with sysrq,
>> remove rule, unload module then add rule i'm getting Oops. Please look
>> at this:
>
> Maybe fixed with commit
> commit cb8050172ae1d893f58c1aa57de975f9932dace6 (v1.44~4)
Hello!
This works for me. Thank you for fix.
Regards,
Marcin
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-09-18 11:20 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-01-20 16:48 [xtables-addons] Oops in SYSRQ, BUG: unable to handle kernel paging request at ffffffffa01a90e0 Marcin Mirosław
2012-01-20 17:14 ` Jan Engelhardt
2012-01-20 18:59 ` Marcin Mirosław
2012-08-23 13:23 ` Jan Engelhardt
2012-09-18 11:20 ` Marcin Mirosław
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).