public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
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 12:36:44 +0100	[thread overview]
Message-ID: <Yfu+TPEQgeC7OJdR@calimero.vinschen.de> (raw)
In-Reply-To: <20220203195949.5842fb4ab2ab901fe4a6f789@nifty.ne.jp>

On Feb  3 19:59, Takashi Yano wrote:
> On Thu, 3 Feb 2022 18:28:32 +0900
> Takashi Yano wrote:
> > 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.
> > > 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
> 
> I have just reconfirmed that this problem does not occur
> if samba under debian stretch is used even with SMB3.11.
> 
> Samba version of stretch is: Version 4.5.16-Debian.

Indeed, I can reproduce it.  I'm using Fedora 35 with Samba 4.15.3,
so there's probably a behavioural change.  The reason I didn't
notice it is that I never use drive letters but always UNC paths.

Thanks!


Corinna

      reply	other threads:[~2022-02-03 11:36 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
2022-02-03 10:59     ` Takashi Yano
2022-02-03 11:36       ` Corinna Vinschen [this message]

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=Yfu+TPEQgeC7OJdR@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).