[linux-cifs-client] Re: Can't mount NAS device

[Steve French (smfltc)]

Naidu Bollineni wrote:

>Could this be due to NULL pointer being passed in cifs_read_inode()
>call?
>
>Is there a special reason for NULL pointer as second argument to
>cifs_get_inode_info(), and cifs_get_inode_info_unix() ? Is there any
>wrong if "\\" is passed?
>
>Thanks
>Naidu.
>
>-----Original Message-----
>From: linux-cifs-client-bounces+naidu=kazeon.com at lists.samba.org
>[mailto:linux-cifs-client-bounces+naidu=kazeon.com at lists.samba.org] On
>Behalf Of Steve French (smfltc)
>Sent: Thursday, March 29, 2007 2:13 PM
>To: linux-cifs-client at lists.samba.org
>Subject: [linux-cifs-client] Re: Can't mount NAS device
>
>strace did show something useful
>    mount(...) = -1 ENOTDIR (Not a directory)
>
>and then that led me to spotting the obvious bug which is
>on your NAS device (server).  The server is returning a
>malformed (illegal) response.
>
>The Linux cifs client was getting a 22 byte response to a level 0x200
>(FILE_UNIX_BASIC_INFO) request that is supposed to be 100 bytes.
>
>.samba.org/mailman/listinfo/linux-cifs-client
>  
>
There would be nothing wrong with passing a /   (or \ if this were 
windows), but whether the path is two
bytes of null or / it resolves to the same thing.   The server did not 
return an SMB error on the call,
it just returned the wrong size response.  

Just a guess ... the server returned a response to a different default 
infolvel when it encounered
a QPathInfo/QFileInfo level it did not understand (instead of returning 
an error not supported smb error)..