netdev - Re: Networking-related crash?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <608c44bf1001050857x3fb75591i6b8976e5018b742@mail.gmail.com>
Date:	Tue, 5 Jan 2010 16:57:48 +0000
From:	Adam Huffman <adam.huffman@...il.com>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	Eric Dumazet <eric.dumazet@...il.com>, Avi Kivity <avi@...hat.com>,
	kvm@...r.kernel.org, netdev <netdev@...r.kernel.org>,
	Netfilter Development Mailinglist 
	<netfilter-devel@...r.kernel.org>
Subject: Re: Networking-related crash?

On Mon, Dec 14, 2009 at 1:16 PM, Patrick McHardy <kaber@...sh.net> wrote:
> Adam Huffman wrote:
>> On Thu, Dec 10, 2009 at 11:01 AM, Patrick McHardy <kaber@...sh.net> wrote:
>>> Eric Dumazet wrote:
>>>> Le 09/12/2009 16:11, Avi Kivity a écrit :
>>>>> On 12/09/2009 03:46 PM, Adam Huffman wrote:
>>>>>> I've been seeing lots of crashes on a new Dell Precision T7500,
>>>>>> running the KVM in Fedora 12.  Finally managed to capture an Oops,
>>>>>> which is shown below (hand-transcribed):
>>>>>>
>>>>>> BUG: unable to handle kernel paging request at 0000000000200200
>>>>>> IP: [<ffffffff8139aab7>] destroy_conntrack+0x82/0x11f
>>>>>> PGD 332d0e067 PUD 33453c067 PMD 0
>>>>>> RIP: 0010:[<ffffffff8139aab7>]  [<ffffffff8139aab7>]
>>>>>> destroy_conntrack+0x82/0x11f
>>>>>> RSP: 0018:ffffc90000803bf0  EFLAGS: 00010202
>>>>>> RAX: 0000000080000001 RBX: ffffffff816fb1a0 RCX: 000000000000752f
>>>>>> RDX: 0000000000200200 RSI: 0000000000000011 RDI: ffffffff816fb1a0
>>>>>> RBP: ffffc90000803c00 R08: ffff880336699438 R09: 0000000000aaa5e0
>>>>>> R10: 00000002f54189d5 R11: 0000000000000001 R12: ffffffff819a92e0
>>>>>> R13: ffffffffa029adcc R14: 0000000000000000 R15: ffff880632866c38
>>>>>> FS:  00007fdd34b17710(0000) GS:ffffc90000800000(0000)
>>>>>> knlGS:0000000000000000
>>>>>> CS:  0010 DS: 002B ES: 002B CR0: 0000000080050033
>>>>>> CR2: 0000000000200200 CR3: 00000003349c0000 CR4: 00000000000026e0
>>>>>> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
>>>>>> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
>>>>>> Process qemu-kvm (pid: 1759, threadinfo ffff88062e9e8000, task
>>>>>> ffff880634945e00)
>>>>>> Stack:
>>>>>>   ffff880632866c00 ffff880634640c30 ffffc90000803c10 ffffffff813989c2
>>>>>> <0>  ffffc90000803c30 ffffffff81374092 ffffc90000803c30 ffff880632866c00
>>>>>> <0>  ffffc90000803c50 ffffffff81373dd3 0000000200000000 ffff880632866c00
>>>>>> Call Trace:
>>>>>>   <IRQ>
>>>>>>   [<ffffffff813989c2>] nf_conntrack_destroy+0x1b/0x1d
>>>>>>   [<ffffffff81374092>] skb_release_head_state+0x95/0xd7
>>>>>>   [<ffffffff81373dd3>] __kfree_skb+0x16/0x81
>>>>>>   [<ffffffff81373ed7>] kfree_skb+0x6a/0x72
>>>>>>   [<ffffffffa029adcc>] ip6_mc_input+0x220/0x230 [ipv6]
>>>>>>   [<ffffffffa029a3d1>] ip6_rcv_finish+0x27/0x2b [ipv6]
>>>>>>   [<ffffffffa029a763>] ipv6_rcv+0x38e/0x3e5 [ipv6]
>>>>>>   [<ffffffff8137bd91>] netif_receive_skb+0x402/0x427
>>>>>>   ...
>>>>>>
>>>> crash in :
>>>>       48 8b 43 08             mov    0x8(%rbx),%rax
>>>>       a8 01                   test   $0x1,%al
>>>>       48 89 02                mov    %rax,(%rdx)  << HERE >> RDX=0x200200  (LIST_POISON2)
>>>>       75 04                   jne    1f
>>>>       48 89 50 08             mov    %rdx,0x8(%rax)
>>>> 1:    48 c7 43 10 00 02 20    movq   $0x200200,0x10(%rbx)
>>>>
>>>>       if (!nf_ct_is_confirmed(ct)) {
>>>>               BUG_ON(hlist_nulls_unhashed(&ct->tuplehash[IP_CT_DIR_ORIGINAL].hnnode));
>>>>               hlist_nulls_del_rcu(&ct->tuplehash[IP_CT_DIR_ORIGINAL].hnnode);  << HERE >>
>>>>       }
>>>>       NF_CT_STAT_INC(net, delete);
>>>
>>> I can't spot the problem. Adam, please send me your .config file.
>>>
>>>
>>
>> It's the standard Fedora .config, which is attached.
>>
>> As I stated in another message, the oops seems related to VT-d.  With
>> that disabled, the machine has been stable for nearly a day now.
>
> That probably only affects the timing of some race. Please also
> send me the IPv6 ruleset used on that machine. Thanks.
>

Just to note that if I disable IPv6 completely, the machine is stable
- certainly compared with the crashes after a few minutes when IPv6 is
enabled.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html