From: Jeremy Allison <jra@samba.org>
To: Igor Mammedov <niallain@gmail.com>
Cc: Jeremy Allison <jra@samba.org>, Steve French <smfrench@gmail.com>,
"Q (Igor Mammedov)" <qwerty0987654321@mail.ru>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-cifs-client@lists.samba.org
Subject: Re: dfs path construction fixup for / character in \\server\share component of dfs path
Date: Fri, 25 Apr 2008 12:22:14 -0700 [thread overview]
Message-ID: <20080425192214.GD28233@samba1> (raw)
In-Reply-To: <48103EF6.7010004@gmail.com>
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 ?
Jeremy.
next prev parent reply other threads:[~2008-04-25 19:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 23:03 dfs path construction fixup for / character in \\server\share component of dfs path Steve French
2008-04-23 14:28 ` Igor Mammedov
2008-04-23 19:11 ` Jeremy Allison
2008-04-23 19:19 ` Jeremy Allison
2008-04-24 8:04 ` Igor Mammedov
2008-04-25 19:22 ` Jeremy Allison [this message]
2008-04-25 19:50 ` Jeremy Allison
2008-04-25 21:16 ` Jeremy Allison
2008-04-27 13:00 ` Igor Mammedov
2008-04-28 18:05 ` Jeremy Allison
2008-04-28 18:51 ` Jeremy Allison
2008-05-21 13:57 ` Igor Mammedov
2008-05-24 0:46 ` Jeremy Allison
2008-05-24 1:33 ` Steve French
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=20080425192214.GD28233@samba1 \
--to=jra@samba.org \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=niallain@gmail.com \
--cc=qwerty0987654321@mail.ru \
--cc=smfrench@gmail.com \
/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.