linux-kernel - Kernel panic with ipsec over ipv6

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>] [day] [month] [year] [list]

Message-ID: <20151020093604.GB13211@scottrix.co.uk>
Date:	Tue, 20 Oct 2015 10:36:04 +0100
From:	Scott Harrison <scott.linux-kernel@...ttrix.co.uk>
To:	linux-kernel@...r.kernel.org
Subject: Kernel panic with ipsec over ipv6

Hi,

I have recently upgraded from 4.1.6 to 4.2.1 and am now seeing a kernel
panic when trying to do IPSec (using ipsec-tools, racoon and setkey) over
IPv6:

Call Trace:
   [<ffffffff8151460c>] ? ip6_dst_destroy+0x5c/0xf0
   [<ffffffff8146343f>] dst_destroy+0x6f/0xd0
   [<ffffffff81463557>] dst_gc_task+0xb7/0x220
   [<ffffffff8100cd13>] ? __switch_to+0x273/0x480
   [<ffffffff8106dd21>] process_on_work+0x141/0340
   [<ffffffff8106df93>] worker_thread+0x73/0x470
   [<ffffffff8106df20>] ? process_on_work+0x340/0x340
   [<ffffffff8106df20>] ? process_on_work+0x340/0x340
   [<ffffffff81073645>] kthread+0xe5/0x100
   [<ffffffff81073560>] ? kthread_create_on_node+0x180/0x180
   [<ffffffff8156059f>] ret_from_fork+0x3f/0x70
   [<ffffffff81073560>] ? kthread_create_on_node+0x180/0x180

Code: 48 81 c4 20 10 00 00 89 c6 e8 bb 3a b3 ff 5d c3 66 0f 1f 84 00 00 00 00 00
   65 81 05 dd bb aa 7e 00 02 00 00 31 c0 ba 01 00 00 00 <f0> 0f b1 17 85 c0 75 01
   c3 55 48 89 e5 48 81 ec 20 10 00 00 48
RIP  [<ffffffff8155fd02>] _raw_spin_lock_bh+0x12/0x40
   RSP <ffff8800bb91bcd0>
CR2: 0000000000000000
---[ end trace ae902d1290b61bc5 ]---
Kernel panic - not syncing: Fatal exception in interrupt
Kernel Offset: disabled
---[ end Kernel panic - not syncing: Fatal exception in interrupt


(I had to copy this by hand from the console, so there may be typos, sorry)

I have done a git bisect on the kernel and found that this started to occur
at 8d0b94afdca84598912347e61defa846a0988d04, if I revert this change in
kernel 4.2.2, then the system works as expected.

Is this the right place to report this, has it been seen before ?

I'm not on the mailing list so please CC me in responses.

Regards,

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