From: Paulo Alcantara <pc@manguebit.org>
To: Matthew Richardson <m.richardson@ed.ac.uk>,
Ralph Boehme <slow@samba.org>
Cc: samba@lists.samba.org, CIFS <linux-cifs@vger.kernel.org>,
Steve French <smfrench@gmail.com>
Subject: Re: [Samba] SMB3 Unix Extensions - creating special files
Date: Thu, 31 Jul 2025 15:15:45 -0300 [thread overview]
Message-ID: <b35e6347503b65febbd0cbec69e52ab1@manguebit.org> (raw)
In-Reply-To: <dbb8e4be-6e90-4ab7-a2d3-52daad3fff2d@ed.ac.uk>
Matthew Richardson <m.richardson@ed.ac.uk> writes:
> Thanks for spotting this. I can confirm that I see different behaviour
> with different kernels:
>
> 6.13.0 - mkfifo and ln-s work as expected.
> 6.14.0 - mkfifo works, ln-s gives 'operation not supported'.
> >=6.15.7 - both give 'operation not supported'.
>
> Which implies possibly more than one regression?
Yes. It used to work on older kernels because the client used to create
special files with NFS reparse points by default, which is required for
SMB3.1.1 POSIX mounts. 6c06be908ca1 ("cifs: Check if server supports
reparse points before using them") then added a check for
FILE_SUPPORTS_REPARSE_POINTS, which breaks against samba because it
isn't set. IOW, we should skip this check for SMB3.1.1 POSIX mounts.
next prev parent reply other threads:[~2025-07-31 18:15 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 [this message]
[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
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=b35e6347503b65febbd0cbec69e52ab1@manguebit.org \
--to=pc@manguebit.org \
--cc=linux-cifs@vger.kernel.org \
--cc=m.richardson@ed.ac.uk \
--cc=samba@lists.samba.org \
--cc=slow@samba.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox