From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 4 Mar 2014 11:46:55 -0800 From: Greg Kroah-Hartman To: Jeff Layton 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: <20140304194655.GC19462@kroah.com> References: <20140225152443.GA15552@sucs.org> <20140225161156.GA27235@kroah.com> <20140225094306.63cccecb@corrin.poochiereds.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140225094306.63cccecb@corrin.poochiereds.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: On Tue, Feb 25, 2014 at 09:43:06AM -0800, Jeff Layton wrote: > 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... It doesn't apply to 3.10 or 3.4-stable trees, so I'll wait for someone to provide a working backport before I can commit it. thanks, greg k-h