From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: path: Fix UNC path handling for SMB3 mounted to a drive.
Date: Thu, 3 Feb 2022 18:28:32 +0900 [thread overview]
Message-ID: <20220203182832.3f0613375ce8eadd2cd27b05@nifty.ne.jp> (raw)
In-Reply-To: <YfuZK5lTopYPSwwZ@calimero.vinschen.de>
On Thu, 3 Feb 2022 09:58:19 +0100
Corinna Vinschen wrote:
> On Feb 3 17:40, Takashi Yano wrote:
> > - If an UNC path is mounted to a drive using SMB3.11, accessing to
> > the drive fails with error "Too many levels of symbolic links."
> > This patch fixes the issue.
>
> LGTM, please push.
Thanks for reviewing.
> I'm curious. I'm using Samba as well and never saw this problem.
> Can you describe how to reproduce?
I used samba under debian stretch last December, and
confirmed current code worked without the problem.
Recently, I have upgraded the server OS from stretch
to bullseye, and noticed this problem.
Perhaps, samba version and its protocol version may be
related.
My samba version is: Version 4.13.13-Debian
This also happens with shared folder under Windows 10
in my environment.
Win10 version is:
Microsoft Windows [Version 10.0.19044.1466]
The reproducible steps are as follows.
$ net use z: '\\server\sharedname'
The command completed successfully.
$ cd /cygdrive/z
/cygdrive/z: Too many levels of symbolic links.
$
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-02-03 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 8:40 Takashi Yano
2022-02-03 8:58 ` Corinna Vinschen
2022-02-03 9:28 ` Takashi Yano [this message]
2022-02-03 10:59 ` Takashi Yano
2022-02-03 11:36 ` Corinna Vinschen
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=20220203182832.3f0613375ce8eadd2cd27b05@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-patches@cygwin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).