[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH2r5mvO+E9ouaEOBL-08pKZXo+C-KdWCsELpiqocLT4itradw@mail.gmail.com>
Date: Tue, 25 Feb 2014 09:29:20 -0600
From: Steve French <smfrench@...il.com>
To: Sitsofe Wheeler <sitsofe@...oo.com>
Cc: stable@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jim McDonough <jmcd@...ba.org>,
Jeff Layton <jlayton@...hat.com>,
David Disseldorp <ddiss@...ba.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: Stable backport of cifs nlink workaround?
The patch is a little larger than usual for stable but for those where
the backport is trivial, seems reasonable candidate for stable.
On Tue, Feb 25, 2014 at 9:24 AM, Sitsofe Wheeler <sitsofe@...oo.com> wrote:
> Hi,
>
> Is there any chance that 74d290da476f672ad756634d12aa707375d3564d
> ([CIFS] Provide sane values for nlink) could be backported to the stable
> 3.2 kernel?
>
> The reason I ask is because if you Using a Debain Wheezy box with a
> 3.2.41-2+deb7u2 kernel the following is problematic:
>
> Mount a share using cifs from a Windows 2008 machine on to 2008share
> Use Samba 3.6 to export the share as //linux/2008share
> Using a Windows 2012 machine browse to \\linux\2008share
>
> because the directories will appear to be files to the Windows 2012
> machine.
>
> On the Debian box doing
> stat 2008share/dir
> says
> Device: 18h/24d Inode: 844424932383132 Links: 1
>
> Using a Fedora 20 box with a 3.13.3-201.fc20.x86_64 kernel to do the
> same says:
> Device: 27h/39d Inode: 844424932383132 Links: 2
>
> In https://bugzilla.kernel.org/show_bug.cgi?id=52791#c4 Jeff mentions
> that if there were demand a RHEL 6 customer could ask for a backport so
> it looks like the change is isolated enough to be put into stable...
>
> https://bugzilla.samba.org/show_bug.cgi?id=9346 also talks about the
> issue.
>
> --
> Sitsofe | http://sucs.org/~sits/
--
Thanks,
Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists