Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751453AbbLMWXB (ORCPT ); Sun, 13 Dec 2015 17:23:01 -0500 Received: from youngberry.canonical.com ([91.189.89.112]:44276 "EHLO youngberry.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751061AbbLMWW7 (ORCPT ); Sun, 13 Dec 2015 17:22:59 -0500 Date: Sun, 13 Dec 2015 22:22:55 +0000 From: Luis Henriques To: David Miller Cc: eric.dumazet@gmail.com, ben@decadent.org.uk, edumazet@google.com, steffen.klassert@secunet.com, linux-kernel@vger.kernel.org, stable@vger.kernel.org, kernel-team@lists.ubuntu.com Subject: Re: [PATCH 3.16.y-ckt 009/126] sit: fix sit0 percpu double allocations Message-ID: <20151213222255.GE31826@charon> References: <20151213185429.GA31826@charon> <1450038035.3944.2.camel@decadent.org.uk> <1450039390.9768.30.camel@edumazet-glaptop2.roam.corp.google.com> <20151213.171406.878570563174220825.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20151213.171406.878570563174220825.davem@davemloft.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 872 Lines: 24 On Sun, Dec 13, 2015 at 05:14:06PM -0500, David Miller wrote: > From: Eric Dumazet > Date: Sun, 13 Dec 2015 12:43:10 -0800 > > > 2) I have no idea why this patch is even backported to 3.16, > > since it is fixing a problem added in 3.18 : > > Because someone on the path to some of the -stable trees aren't even > checking the Fixes: tag in the patches they are backporting. > > And that's really bad... As I already said before, this patch has been included in 3.16 because the SHA1 in the "Fixes:" *is* in 3.16 (as it is in other even older stable trees such as 3.12 and 3.14). Cheers, -- Lu?s -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/