Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753489AbaBYRnZ (ORCPT ); Tue, 25 Feb 2014 12:43:25 -0500 Received: from mx1.redhat.com ([209.132.183.28]:59521 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753193AbaBYRnY (ORCPT ); Tue, 25 Feb 2014 12:43:24 -0500 Date: Tue, 25 Feb 2014 09:43:06 -0800 From: Jeff Layton To: Greg Kroah-Hartman Cc: Sitsofe Wheeler , stable@vger.kernel.org, linux-kernel@vger.kernel.org, Jim McDonough , David Disseldorp , Steve French , Alan Cox Subject: Re: Stable backport of cifs nlink workaround? Message-ID: <20140225094306.63cccecb@corrin.poochiereds.net> In-Reply-To: <20140225161156.GA27235@kroah.com> References: <20140225152443.GA15552@sucs.org> <20140225161156.GA27235@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 25 Feb 2014 08:11:56 -0800 Greg Kroah-Hartman wrote: > On Tue, Feb 25, 2014 at 03:24:43PM +0000, Sitsofe Wheeler wrote: > > Hi, > > > > Is there any chance that 74d290da476f672ad756634d12aa707375d3564d > > ([CIFS] Provide sane values for nlink) could be backported to the stable > > 3.2 kernel? > > Why just 3.2? What's wrong with all of the other kernels before 3.12 > that do not have this patch in it? > > thanks, > > greg k-h Yeah, you'd probably need to apply it to every stable kernel > 3.2 or you'd technically have a regression. I've no real objection to putting that fix in, but backporting to older kernels may not be trivial. There have been other changes in this area over the years... -- Jeff Layton -- 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/