All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralph Boehme <slow@samba.org>
To: Steve French <smfrench@gmail.com>,
	samba-technical <samba-technical@lists.samba.org>
Cc: CIFS <linux-cifs@vger.kernel.org>,
	Namjae Jeon <linkinjeon@kernel.org>,
	Jeremy Allison <jra@samba.org>
Subject: Re: Missing protocol features that could help Linux
Date: Fri, 19 Apr 2024 18:53:01 +0200	[thread overview]
Message-ID: <e69bad72-9139-4b01-afe5-5d34edc077a1@samba.org> (raw)
In-Reply-To: <CAH2r5mstDacz=gvpjFQeB_nc1kBjyzTZw57tF8UNrXARXkV1rQ@mail.gmail.com>


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

On 4/18/24 22:21, Steve French via samba-technical wrote:
> Was following up on a recent question about support for Linux features
> that are missing that could help us pass more xfstests
> 
> Looking at the standard fstests for Linux (xfstests that are skipped
> or fail for cifs.ko) to find 'features' that would help, perhaps
> extending the current POSIX Extensions or adding a couple of SMB3.1.1
> FSCTLs, I spotted a few obvious ones:
> 
>   1) renameat2 (RENAME_EXCHANGE) and renameat2(WHITEOUT)  2) FITRIM
> support 3) trusted namespace (perhaps xattr/EA extension) 4) attr
> namespace 5) deduplication 6) chattr -i 7) unshare (namespace command)
> 8) delayed allocation 9) dax 10) attr namespace security 11) fstrim
> 12) chattr +s 13) exchange range
> 
> Any thoughts on which of these which would be 'easy' for samba and/or
> ksmbd server to implement (e.g. as new fsctls)?

well, I guess none of these will be really "easy".

Iirc when I last brough up file attributes, we vetted towards postponing 
this kind of stuff until we have full support for the core SMB3 POSIX 
features in Samba. Iirc the only real thing missing there is 
symlink/reparse point handling and for that we need to settle on which 
reparse type to use (WSL vs NFS) as discussed yesterday. It would be a 
*huge* help Steve, if you can pursue this internally, this has been a 
blocker for the whole project since quite some time...

-slow


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

  parent reply	other threads:[~2024-04-19 16:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 20:21 Missing protocol features that could help Linux Steve French
2024-04-19  1:40 ` Andrew Bartlett
2024-04-19 15:55   ` Jeremy Allison
2024-04-19 15:58     ` Ralph Boehme
2024-04-19 17:12     ` Steve French
2024-04-19 16:53 ` Ralph Boehme [this message]
2024-04-19 16:55   ` Jeremy Allison

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=e69bad72-9139-4b01-afe5-5d34edc077a1@samba.org \
    --to=slow@samba.org \
    --cc=jra@samba.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=samba-technical@lists.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 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.