Bug 503040 – sys-kernel/gentoo-sources-3.13.5 - kernel panic using nftables' log

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description William 2014-02-28 13:13:41 UTC]

Nftables works fine as long as you don't enable logging.
Something like this: 

table firewall {
        chain incoming {
                type filter hook input priority 0;
                        ip protocol icmp drop
                        accept
        }
}

Ping the interface, the kernel panics in ipt_log_fn, nf_log_packet.



Reproducible: Always

Steps to Reproduce:
1. add rule in nftables that logs an event
2. trigger rule
3. watch machine die
Actual Results:  
kernel panic

Expected Results:  
no kernel panic

I'll attach my .config.

[Comment 1 William 2014-02-28 13:14:46 UTC]

Created attachment 371426 [details]
my .config

[Comment 2 William 2014-02-28 13:16:54 UTC]

Oh, the nftables rule I quoted works because no logging is requested. This would kernel panic:


table firewall {
        chain incoming {
                type filter hook input priority 0;
                        ip protocol icmp log drop
                        accept
        }
}

And the a ping results to "kernel panic not syncing, Fatal exception in interrupt"

[Comment 3 Mike Pagano 2014-03-07 20:01:16 UTC]

Can I see the panic, please? Maybe the full dmesg and also your emerge --info