Re: System freeze on reboot - general protection fault

From: Zdenek Kabelac
Date: Thu Aug 13 2009 - 13:09:15 EST


2009/8/13 Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx>:
> On Thu, 13 Aug 2009, Zdenek Kabelac wrote:
>
>> > I've added authors of some recent conntrack commits to Cc: - maybe
>> > they might know?
>>
>> I've tested v2.6.30 - and it's crashing in the same way - so any other
>> starting point where slub has the same detection mechanism and
>> conntrack module should be working reliable ?
>
> Next point is 2.6.29.
>

Ok - played lengthy game between 2.6.29 which appeared to be ok and 2.6.30

And the winner is: ea781f197d6a835cbb93a0bf88ee1696296ed8aa
netfilter: nf_conntrack: use SLAB_DESTROY_BY_RCU and get rid of call_rcu()

The error is actually being hit by libvirtd networking rules added
during boot for my kvm usage.
(Which I noticed after some time... leading my game into wrong
direction ;))....

Here are the some last bisect entries:

git bisect bad 54dc79fe0d895758bdaa1dcf8512d3d21263d105
# bad: [5c0de29d06318ec8f6e3ba0d17d62529dbbdc1e8] netfilter:
nf_conntrack: add generic function to get len of generic policy
git bisect bad 5c0de29d06318ec8f6e3ba0d17d62529dbbdc1e8
# good: [e487eb99cf9381a4f8254fa01747a85818da612b] netlink: add nla_policy_len()
git bisect good e487eb99cf9381a4f8254fa01747a85818da612b
# good: [1f9352ae2253a97b07b34dcf16ffa3b4ca12c558] netfilter:
{ip,ip6,arp}_tables: fix incorrect loop detection
git bisect good 1f9352ae2253a97b07b34dcf16ffa3b4ca12c558
# bad: [2732c4e45bb67006fdc9ae6669be866762711ab5] netfilter:
ctnetlink: allocate right-sized ctnetlink skb
git bisect bad 2732c4e45bb67006fdc9ae6669be866762711ab5


Unfortunately the commit cannot be reverted with current tree - thus I
cannot easily check if it's the only problem.
(warning: too many files (created: 3096 deleted: 1096), skipping
inexact rename detection
Automatic revert failed. After resolving the conflicts,)

Zdenek
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/