. and .. on search results

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

 



There are cases in which servers fails to return . and .. in search (readdir) results over CIFS. In particular Windows servers which export the root of a drive.

Is returning . and .. in readdir results always required (ie a client change is necessary to insert them if they were not returned)? and do . and .. have to be first in the list of entries in the directory (which would be very inconvenient since I may have to read through all of the directory search results)? Although . and .. are usually returned in the first of what could be many search (Transact2 FindNext) responses from the server, I don't think it is required.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux