From: Jeremy Allison <jra@samba.org>
To: samba@lists.samba.org, linux-cifs@vger.kernel.org
Subject: Re: [Samba] SMB3 Unix Extensions - creating special files
Date: Mon, 2 Mar 2026 17:13:22 -0800 [thread overview]
Message-ID: <901186d6-ade6-4949-9a1e-773c082cc5cf@samba.org> (raw)
In-Reply-To: <63195a70-5978-4389-8016-6f2591d262d6@math.lsu.edu>
On 3/2/26 4:41 PM, Nikkos Svoboda via samba wrote:
>
> Jumping in here briefly, I believe the "default" symlink style
> requested by the client mount options is now "symlink=native", which
> creates the 0-sized files with extended attributes on the server.
>
> I'd also like to know: Is it intended to allow creation of "actual"
> symlinks on a supported server filesystem via unix 3.1.1 Extensions? The
> mount option "symlink=unix" (which creates "actual" symlinks on the
> server), when used with SMB 3.1.1 unix extensions, causes symlink
> creation to fail on the client with "Operation not supported" (client
> kernel 6.17, ubuntu 24.04). That mount option appears to be referred to
> as "SMB1 unix create symlink command" which I presume means it is
> limited to the SMB1 unix extensions.
>
> The archived e-mail conversation chain here (though it includes some
> outdated information) helped me to understand some of what the symlink=
> and reparse= mount options were intended for:
> https://lwn.net/ml/all/20241007183650.aw3skuztljpgk2bs@pali/
The goal (at least when I was involved with this effort) was to
explicitly *ban* SMB3 UNIX extensions ever from creating server-side
symlinks.
Such activities are inherently unsafe and a source of many, many
CVE's.
next prev parent reply other threads:[~2026-03-03 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1124e7cd-6a46-40a6-9f44-b7664a66654b@ed.ac.uk>
[not found] ` <7082aea3-b28b-4ef5-9b5c-64d5d8b78cbc@samba.org>
[not found] ` <a4a32c8e-3b7f-4748-8c50-48f18e8980b9@ed.ac.uk>
2025-07-31 16:12 ` [Samba] SMB3 Unix Extensions - creating special files Ralph Boehme
2025-07-31 16:18 ` Steve French
2025-07-31 17:37 ` Paulo Alcantara
2025-07-31 18:03 ` Matthew Richardson
2025-07-31 18:15 ` Paulo Alcantara
[not found] ` <CAH2r5mt_9GcPqg+v9QLXEroKJ9RQZ1MwtpPgprU+xHOSksiWqw@mail.gmail.com>
2025-07-31 19:24 ` Matthew Richardson
2025-07-31 20:00 ` Paulo Alcantara
2026-03-02 15:09 ` Matthew Richardson
2026-03-03 0:41 ` Nikkos Svoboda
2026-03-03 1:13 ` Jeremy Allison [this message]
2026-03-03 2:29 ` Jim DeLaHunt
2025-07-31 19:59 ` Paulo Alcantara
2025-07-31 19:20 ` Ralph Boehme
2025-07-31 19:55 ` Paulo Alcantara
[not found] ` <notmuch-sha1-71ace0e0808cb1155c98f212b8406ee293b20f11>
2025-07-31 18:00 ` Paulo Alcantara
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=901186d6-ade6-4949-9a1e-773c082cc5cf@samba.org \
--to=jra@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=samba@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox