[Xen-bugs] [Bug 1361] New: Kernel BUG at ...en-3.3.0/linux-2.6.18-xen.hg/net/ipv6/ip6_output.c:699

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1361

           Summary: Kernel BUG at ...en-3.3.0/linux-2.6.18-
                    xen.hg/net/ipv6/ip6_output.c:699
           Product: Xen
           Version: 3.0 (general)
          Platform: x86-64
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: grgtlr5@xxxxxxxxxxxxxx


An interaction between named (serving DNSSEC enabled zones, ie larger than
usual DNS packets), IPSEC, and IPv6 seems to cause either the kernel bug output
below, and/or named to hang, not logging or responding to queries and refusing
to die (kill -9 results in a defunct process).

Xen v3.2.0 and v3.3.0 (from source from xen.org)
Linux v2.6.18 (from source fetched by Xen)
Debian etch amd64 (dom0 and domU)
BIND 9.3.4-2etch3

BIND9 is configured to answer queries on localhost (IPv4&6) recursively, and
public IPv4 and IPv6 addresses (authoritative only). A slave server is on a
remote server, racoon and setkey policy require is used to force IPSEC between
the master and slave.

Since signing several zones with DNSSEC, named will occasionally stop
responding to queries, kill has no effect, kill -9 results in a defunct
process. Failure seems to be triggered by an interaction with IPSEC, especially
when the remote server is down and the IPSEC tunnel is unavailable.

Network MTU is 1500, but IPv6 is over a tunnel (1480), and IPSEC adds further
overhead. With DNSSEC some DNS responses exceed 1500 bytes.


kernel log output from domU:

Kernel BUG at ...en-3.3.0/linux-2.6.18-xen.hg/net/ipv6/ip6_output.c:699
invalid opcode: 0000 [1] SMP 
CPU 3 
Pid: 941, comm: named Not tainted 2.6.18.8-xenU #1
RIP: e030:[<ffffffff802941f6>]  [<ffffffff802941f6>]
RSP: e02b:ffff88007e36ba08  EFLAGS: 00010282
RAX: 00000000fffffff2 RBX: ffff88005c056880 RCX: 00000000000000c2
RDX: ffff88005e474e00 RSI: 00000000000007d0 RDI: ffff88006224de80
RBP: ffff88005e474800 R08: 2d36320a4345534e R09: 00002b74763d4b36
R10: 00002b74763d4b3b R11: 00002b74763d4b2c R12: 00000000fffffdf0
R13: 00000000fffffeb2 R14: ffff88006224de80 R15: 00000000000007d0
FS:  0000000000000000(0063) GS:ffffffff8033d180(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process named (pid: 941, threadinfo ffff88007e36a000, task ffff88007fdf6080)
Stack:  000007d0803b7510 a800000068244fd9 ffff88007e5e61c0 ffff880080000000
 fffffdf000000000 00000000000000c2 ffff88005e474868 ffff88006224de80
 ffff88007ea0eac0 ffff88007ea0ed98 ffff88007ea0ed40 ffff88007e5e61c0
Call Trace:
 [<ffffffff80294849>]
 [<ffffffff802959cf>]
 [<ffffffff802a5de5>]
 [<ffffffff802a767a>]
 [<ffffffff8014b84c>]
 [<ffffffff8022a7b5>]
 [<ffffffff8012fbe2>]
 [<ffffffff8013f247>]
 [<ffffffff8015d00c>]
 [<ffffffff801424eb>]
 [<ffffffff80142a5c>]
 [<ffffffff8022e3b5>]
 [<ffffffff8022b093>]
 [<ffffffff80144525>]
 [<ffffffff8010a064>]
 [<ffffffff80109ffc>]


Code: 0f 0b 68 98 4e 30 80 c2 bb 02 0f b7 44 24 20 89 c2 c1 e2 08 
RIP  [<ffffffff802941f6>]
 RSP <ffff88007e36ba08>


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs