From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jim McDonough <jmcd@samba.org>, Jeff Layton <jlayton@redhat.com>,
David Disseldorp <ddiss@samba.org>,
Steve French <smfrench@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Stable backport of cifs nlink workaround?
Date: Tue, 25 Feb 2014 15:24:43 +0000 [thread overview]
Message-ID: <20140225152443.GA15552@sucs.org> (raw)
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/
next reply other threads:[~2014-02-25 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 15:24 Sitsofe Wheeler [this message]
2014-02-25 15:29 ` Stable backport of cifs nlink workaround? Steve French
2014-02-25 16:11 ` Greg Kroah-Hartman
2014-02-25 17:43 ` Jeff Layton
2014-02-25 18:49 ` Sitsofe Wheeler
2014-03-04 19:46 ` Greg Kroah-Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140225152443.GA15552@sucs.org \
--to=sitsofe@yahoo.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ddiss@samba.org \
--cc=gregkh@linuxfoundation.org \
--cc=jlayton@redhat.com \
--cc=jmcd@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.com \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.