From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753918AbbH0QaW (ORCPT ); Thu, 27 Aug 2015 12:30:22 -0400 Received: from mail-pa0-f42.google.com ([209.85.220.42]:33013 "EHLO mail-pa0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751401AbbH0QaU (ORCPT ); Thu, 27 Aug 2015 12:30:20 -0400 Message-ID: <1440693016.8932.41.camel@edumazet-glaptop2.roam.corp.google.com> Subject: Re: ip_rcv_finish() NULL pointer and possibly related Oopses From: Eric Dumazet To: Michael Marineau Cc: Chuck Ebbert , Shaun Crampton , linux-kernel@vger.kernel.org, Peter White , netdev@vger.kernel.org Date: Thu, 27 Aug 2015 09:30:16 -0700 In-Reply-To: References: <20150826074959.48aea34c@as> <1440680401.8932.39.camel@edumazet-glaptop2.roam.corp.google.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.10.4-0ubuntu2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2015-08-27 at 09:16 -0700, Michael Marineau wrote: > > Oh, interesting. Looks like that patch didn't get CC'd to stable > though, is there a reason for that or just oversight? We never CC stable for networking patches. David Miller prefers to take care of this himself. ( this is in Documentation/networking/netdev-FAQ.txt ) Q: How can I tell what patches are queued up for backporting to the various stable releases? A: Normally Greg Kroah-Hartman collects stable commits himself, but for networking, Dave collects up patches he deems critical for the networking subsystem, and then hands them off to Greg. There is a patchworks queue that you can see here: http://patchwork.ozlabs.org/bundle/davem/stable/?state=* It contains the patches which Dave has selected, but not yet handed off to Greg. If Greg already has the patch, then it will be here: http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git A quick way to find whether the patch is in this stable-queue is to simply clone the repo, and then git grep the mainline commit ID, e.g. stable-queue$ git grep -l 284041ef21fdf2e releases/3.0.84/ipv6-fix-possible-crashes-in-ip6_cork_release.patch releases/3.4.51/ipv6-fix-possible-crashes-in-ip6_cork_release.patch releases/3.9.8/ipv6-fix-possible-crashes-in-ip6_cork_release.patch stable/stable-queue$