This is the initial report I got: [ 2886.953175] BUG: unable to handle kernel paging request at 00100100 [ 2886.956435] IP: [<f88a4ab8>] flush_expectations+0x68/0x85 [nf_conntrack_sip] [ 2886.956435] *pde = 00000000 [ 2886.956435] Oops: 0000 [001] SMP ... [ 2886.956435] Pid: 5606, comm: red_server.plc Tainted: G O 3.3.8-79.g20f5c30-smp 001 Astaro AG ASG/i845GV-W83627HF [ 2886.956435] EIP: 0060:[<f88a4ab8>] EFLAGS: 00210246 CPU: 0 [ 2886.956435] EIP is at flush_expectations+0x68/0x85 [nf_conntrack_sip] [ 2886.956435] EAX: 00000000 EBX: 00100100 ECX: 00000000 EDX: effdc0a0 [ 2886.956435] ESI: 00100100 EDI: 00000001 EBP: 00000001 ESP: f5c0bd54 [ 2886.956435] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 2886.956435] Process red_server.plc (pid: 5606, ti=f5c0a000 task=f5da2a20 task.ti=efc62000) [ 2886.956435] Stack: [ 2886.956435] f490b948 00000001 00000197 f45f4f00 f88a5918 f5c0bde0 f5c0bddc 0000001c [ 2886.956435] 00000014 f88a72a8 0000015d f5c0bddc 00000001 f88a472e f5c0bddc f5c0bde0 [ 2886.956435] 00000001 00000197 00000014 f490b948 f45f4f00 f88a72a8 00000197 00000001 Which is due to nf_conntrack_expect.lnode hlist entry not being reset to NULL after being removed from the list in hlist_del(), but instead to LIST_POISON1. And because of this hlist_for_each_entry_safe() does not terminate correctly. Therefore change nf_ct_unlink_expect_report() to use __hlist_del() instead. Signed-off-by: Holger Eitzenberger <holger@xxxxxxxxxxxxxxxx> Index: linux-stable-3.8.y/net/netfilter/nf_conntrack_expect.c =================================================================== --- linux-stable-3.8.y.orig/net/netfilter/nf_conntrack_expect.c +++ linux-stable-3.8.y/net/netfilter/nf_conntrack_expect.c @@ -51,7 +51,7 @@ void nf_ct_unlink_expect_report(struct n hlist_del_rcu(&exp->hnode); net->ct.expect_count--; - hlist_del(&exp->lnode); + __hlist_del(&exp->lnode); master_help->expecting[exp->class]--; nf_ct_expect_event_report(IPEXP_DESTROY, exp, pid, report); -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
