From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751501Ab3KRJXc (ORCPT ); Mon, 18 Nov 2013 04:23:32 -0500 Received: from a.mx.secunet.com ([195.81.216.161]:33059 "EHLO a.mx.secunet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751082Ab3KRJXH (ORCPT ); Mon, 18 Nov 2013 04:23:07 -0500 Date: Mon, 18 Nov 2013 10:22:55 +0100 From: Steffen Klassert To: David Miller Cc: pomac@demius.net, bhelgaas@google.com, pomac@vapor.com, linux-kernel@vger.kernel.org, edumazet@google.com, netdev@vger.kernel.org, alex.aring@gmail.com Subject: Re: [OOPS][3.12] BUG: unable to handle kernel NULL pointer dereference at 0000000c Message-ID: <20131118092255.GX31491@secunet.com> References: <20131115.174426.1448825246187940374.davem@davemloft.net> <20131115233919.GB11450@pomac.netswarm.net> <20131115.185755.1752342950675745464.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131115.185755.1752342950675745464.davem@davemloft.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-OriginalArrivalTime: 18 Nov 2013 09:22:56.0104 (UTC) FILETIME=[C3E63680:01CEE43F] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 15, 2013 at 06:57:55PM -0500, David Miller wrote: > From: Ian Kumlien > Date: Sat, 16 Nov 2013 00:39:19 +0100 > > > On Fri, Nov 15, 2013 at 05:44:26PM -0500, David Miller wrote: > >> From: Bjorn Helgaas > >> Date: Fri, 15 Nov 2013 15:29:53 -0700 > >> > >> > [+cc David, Eric, Alex, netdev] > >> > > >> > Alex reported a similar issue at > >> > http://marc.info/?l=linux-netdev&m=138355719901790&w=4 > >> > >> Fixed by: > >> > >> commit 84502b5ef9849a9694673b15c31bd3ac693010ae > >> Author: Steffen Klassert > >> Date: Wed Oct 30 11:16:28 2013 +0100 > > > > Cherry-picked, compiled and preparing for reboot - thanks! > > > > Shouldn't this be queued up in stable sometime soonish? > > > > (Sorry for the change of email address, i had forgot to switch the > > configurations in mutt) > > Steffen is in charge of IPSEC -stable submissions, please ask him > :-) It was intended for v3.12 but the release came before it was merged into the manline. So yes, it should go to the v3.12 stable tree. I've always did stable submissions just by marking them as a candidate for stable, this did not happen here because I hoped it will make it into v3.12. It should apply cleanly to v3.12 stable, you could just pick it into you stable queue, or alternatively I can submit to stable.