Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752270AbbJTLBe (ORCPT ); Tue, 20 Oct 2015 07:01:34 -0400 Received: from b.painless.aa.net.uk ([81.187.30.52]:43011 "EHLO b.painless.aa.net.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751651AbbJTLBd (ORCPT ); Tue, 20 Oct 2015 07:01:33 -0400 X-Greylist: delayed 5120 seconds by postgrey-1.27 at vger.kernel.org; Tue, 20 Oct 2015 07:01:32 EDT Date: Tue, 20 Oct 2015 10:36:04 +0100 From: Scott Harrison To: linux-kernel@vger.kernel.org Subject: Kernel panic with ipsec over ipv6 Message-ID: <20151020093604.GB13211@scottrix.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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: [] ? ip6_dst_destroy+0x5c/0xf0 [] dst_destroy+0x6f/0xd0 [] dst_gc_task+0xb7/0x220 [] ? __switch_to+0x273/0x480 [] process_on_work+0x141/0340 [] worker_thread+0x73/0x470 [] ? process_on_work+0x340/0x340 [] ? process_on_work+0x340/0x340 [] kthread+0xe5/0x100 [] ? kthread_create_on_node+0x180/0x180 [] ret_from_fork+0x3f/0x70 [] ? 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 0f b1 17 85 c0 75 01 c3 55 48 89 e5 48 81 ec 20 10 00 00 48 RIP [] _raw_spin_lock_bh+0x12/0x40 RSP 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