[Samba] Re: major cifs bug in 2.6.19+?
joshkel at gmail.com
Mon Apr 30 13:58:12 GMT 2007
On 4/30/07, Jason Haar <Jason.Haar at trimble.co.nz> wrote:
> I can see Linux asking for "ASG_SUPP\*" when I did an "ls -l ASG_SUPP" -
> and I can see the Windows file server returning the contents of the
> directory above it!!!
> //server/share contains 74 subdirectories: attempts to do listings on
> any of those directories results in the same list of 74 top-level
> subdirs again.
> So maybe this problem only hits servers with DFS enabled? But it works
> under 2.6.18...?
When DFS is enabled, the SMB protocol requires that the client send
the full path to the network share (including server), rather than
just the directory (e.g., \\server\share\parent\subdir1 instead of
just parent\subdir1). This lets the DFS server know what DFS root was
originally requested. The CIFS client fails to do that; it instead
just sends parent\subdir1, which causes parent to be interpreted as a
server name and subdir1 as a share name. This is why searching for
parent\subdir1\parent\subdir1 works; the initial "parent\subdir1" is
parsed out as the server and share, then parent\subdir1 is correctly
processed as the path. (If I remember correctly - it's been a little
while since I looked at this.)
I reported this as a bug a while ago, but it apparently hasn't been
fixed yet. See https://bugzilla.samba.org/show_bug.cgi?id=4066.
More information about the samba