Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Ralph Boehme <slow@samba.org>
To: Interoperability Documentation Help <dochelp@microsoft.com>
Cc: "Steve French" <smfrench@gmail.com>,
	"Tom Talpey" <tom@talpey.com>, "Pali Rohár" <pali@kernel.org>,
	CIFS <linux-cifs@vger.kernel.org>
Subject: Fwd: SMB2 DELETE vs UNLINK
Date: Wed, 9 Apr 2025 08:50:59 +0200	[thread overview]
Message-ID: <6f5031e9-36d4-4521-a07a-6892cc5ce8a3@samba.org> (raw)
In-Reply-To: <20250408224309.kscufcpvgiedx27v@pali>


[-- Attachment #1.1: Type: text/plain, Size: 2401 bytes --]

Hello dochelp,

it seems the updates for POSIX unlink and rename made it into MS-FSCC

<https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/f1f88b22-15c6-4081-a899-788511ae2ed9>

but I don't see accompanying updates to MS-FSA and, if supported over 
SMB, MS-SMB2.

Is this coming? If this is supported over SMB by Windows it is not 
sufficient to have it burried in MS-FSCC. :)

Thanks!
-slow

-------- Forwarded Message --------
Subject: Re: SMB2 DELETE vs UNLINK
Date: Wed, 9 Apr 2025 00:43:09 +0200
From: Pali Rohár <pali@kernel.org>
To: linux-cifs@vger.kernel.org
CC: Tom Talpey <tom@talpey.com>, Steve French <sfrench@samba.org>, Paulo 
Alcantara <pc@manguebit.com>, Namjae Jeon <linkinjeon@kernel.org>, Ralph 
Boehme <slow@samba.org>

On Friday 27 December 2024 19:51:30 Pali Rohár wrote:
> On Friday 27 December 2024 11:43:58 Tom Talpey wrote:
> > On 12/27/2024 11:32 AM, Pali Rohár wrote:
> > > On Friday 27 December 2024 11:21:49 Tom Talpey wrote:
> > > > Feel free to raise the issue yourself! Simply email "dochelp@microsoft.com".
> > > > Send as much supporting evidence as you have gathered.
> > > > 
> > > > Tom.
> > > 
> > > Ok. I can do it. Should I include somebody else into copy?
> > 
> > Sure, you may include me, tell them I sent you. :)
> > 
> > Tom.
> > 
> 
> Just note for others that I have already sent email to dochelp.

Hello, I have good news!

dochelp on 04/07/2025 updated MS-FSCC documentation and now it contains
the structures to issue the POSIX UNLINK and RENAME operations.

https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/f1f88b22-15c6-4081-a899-788511ae2ed9
MS-FSCC 7 Change Tracking

https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/2e860264-018a-47b3-8555-565a13b35a45
MS-FSCC 2.4.12 FileDispositionInformationEx has 
FILE_DISPOSITION_POSIX_SEMANTICS

https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/4217551b-d2c0-42cb-9dc1-69a716cf6d0c
MS-FSCC 2.4.43 FileRenameInformationEx has FILE_RENAME_REPLACE_IF_EXISTS 
+ FILE_RENAME_POSIX_SEMANTICS

https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-fscc/ebc7e6e5-4650-4e54-b17c-cf60f6fbeeaa
MS-FSCC 2.5.1 FileFsAttributeInformation has 
FILE_SUPPORTS_POSIX_UNLINK_RENAME

So now both classic Windows DELETE and POSIX UNLINK is available and
documented.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]

  reply	other threads:[~2025-04-09  6:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-06 10:31 SMB2 DELETE vs UNLINK Pali Rohár
2024-10-07  4:18 ` Steve French
2024-10-07 18:48   ` Pali Rohár
2024-10-08  0:07     ` Steve French
2024-10-08  9:40 ` Ralph Boehme
2024-10-08 18:18   ` Pali Rohár
2024-10-08 20:16     ` Ralph Boehme
2024-10-09  5:03     ` Steve French
2024-10-14  9:49       ` Pali Rohár
2024-12-27 15:58         ` Pali Rohár
2024-12-27 16:30           ` Tom Talpey
2024-12-25 14:47 ` Pali Rohár
2024-12-27 16:21   ` Tom Talpey
2024-12-27 16:32     ` Pali Rohár
2024-12-27 16:43       ` Tom Talpey
2024-12-27 18:51         ` Pali Rohár
2025-04-08 22:43           ` Pali Rohár
2025-04-09  6:50             ` Ralph Boehme [this message]
2025-04-09 15:57               ` [EXTERNAL] Fwd: SMB2 DELETE vs UNLINK - TrackingID#2504090040009564 Michael Bowen
2025-04-10  5:57                 ` Tom Talpey
2025-04-10 11:07                 ` Obaid Farooqi
2025-05-06 19:00                   ` Obaid Farooqi
2025-08-31 12:55                     ` Pali Rohár

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=6f5031e9-36d4-4521-a07a-6892cc5ce8a3@samba.org \
    --to=slow@samba.org \
    --cc=dochelp@microsoft.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=pali@kernel.org \
    --cc=smfrench@gmail.com \
    --cc=tom@talpey.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