Re: Stable backport of cifs nlink workaround?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> 
> > On Tue, Feb 25, 2014 at 03:24:43PM +0000, Sitsofe Wheeler wrote:
> > > 
> > > 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?
> 
> 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...

There's no reason why it should only be 3.2 only - the only reason I
picked that one is because it is the current Debian stable kernel. 

-- 
Sitsofe | http://sucs.org/~sits/
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]