Re: dfs path construction fixup for / character in \\server\share component of dfs path

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

 



On Fri, Apr 25, 2008 at 12:22:14PM -0700, Jeremy Allison wrote:
> On Thu, Apr 24, 2008 at 12:04:06PM +0400, Igor Mammedov wrote:
> 
> > I'm doing the second call with a short path to get inode info
> > including server generated inode number. If not for the last 
> > then second call could be omitted and inode be filled with fake
> > values and locally generated ino.
> > 
> > PS:
> > Windows server does not object against the second call and returns
> > info on the dfs junction point (as directory). 
> > More uniform behavior between different implementations would be
> > better for all.
> 
> Very important question here. Do you set the FLAGS2_DFS_PATHNAMES
> bit in the flags2 when you do this QPATHINFO call on the short path ?

Actually, all these questions would be answered if you'd just
forward me the binary wireshark trace you have here.

Thanks !

Jeremy.
--
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