From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 14454] New: cannot get symlink file attributes and target with cifsacl mount option
Date: Mon, 03 Aug 2020 12:19:20 +0000 [thread overview]
Message-ID: <bug-14454-10630@https.bugzilla.samba.org/> (raw)
https://bugzilla.samba.org/show_bug.cgi?id=14454
Bug ID: 14454
Summary: cannot get symlink file attributes and target with
cifsacl mount option
Product: CifsVFS
Version: 3.x
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: kernel fs
Assignee: sfrench@samba.org
Reporter: aaptel@samba.org
QA Contact: cifs-qa@samba.org
Target Milestone: ---
On a Windows Server 2019 share with symlinks:
C:\shares\data> dir
...
12/16/2019 08:04 AM <SYMLINKD> DIR [sub\dir]
12/16/2019 08:04 AM <SYMLINK> foolink.txt [sub\dir\foo.txt]
...
Mounting without cifsacl kind of works (still missing mode bits):
# mount //nuc.test/data /mnt -o username=user1,password=user1,vers=3.0
# ls -la /mnt
total 3148410
...
l--------- 1 root root 0 Dec 16 2019 DIR -> sub/dir
l--------- 1 root root 0 Dec 16 2019 foolink.txt ->
sub/dir/foo.txt
Mounting with cifsacl (with working idmap):
# mount //nuc.test/data /mnt -o
username=user1,password=user1,vers=3.0,cifsacl
# ls -la /mnt
ls: cannot access '/mnt/DIR': Operation not supported
ls: cannot access '/mnt/foolink.txt': Operation not supported
...
d????????? ? ? ? ? ? DIR
-????????? ? ? ? ? ?
foolink.txt
--
You are receiving this mail because:
You are the QA Contact for the bug.
next reply other threads:[~2020-08-03 12:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 12:19 samba-bugs [this message]
2020-08-03 12:19 ` [Bug 14454] cannot get symlink file attributes and target with cifsacl mount option samba-bugs
2020-08-03 12:20 ` samba-bugs
2020-08-03 12:21 ` samba-bugs
2020-08-03 12:21 ` samba-bugs
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=bug-14454-10630@https.bugzilla.samba.org/ \
--to=samba-bugs@samba.org \
--cc=cifs-qa@samba.org \
/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.