linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <pali@kernel.org>
To: Steve French <smfrench@gmail.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	Amir Goldstein <amir73il@gmail.com>,
	ronnie sahlberg <ronniesahlberg@gmail.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org, linux-cifs@vger.kernel.org,
	linux-kernel@vger.kernel.org, Steve French <sfrench@samba.org>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Subject: Re: Immutable vs read-only for Windows compatibility
Date: Fri, 17 Jan 2025 18:57:55 +0100	[thread overview]
Message-ID: <20250117175755.lctf5ezhhtdznt6m@pali> (raw)
In-Reply-To: <CAH2r5mvCJ=fPt5BgwFubJ+HWo+a0EHOTNoXxTt0NOhMC=V+GcQ@mail.gmail.com>

On Friday 17 January 2025 11:51:54 Steve French wrote:
> On Fri, Jan 17, 2025 at 11:39 AM Darrick J. Wong <djwong@kernel.org> wrote:
> >
> > On Fri, Jan 17, 2025 at 05:53:34PM +0100, Amir Goldstein wrote:
> > > On Wed, Jan 15, 2025 at 12:59 AM Darrick J. Wong <djwong@kernel.org> wrote:
> <...>
> > > Looking at the FILE_ATTRIBUTE_* flags defined in SMB protocol
> > >  (fs/smb/common/smb2pdu.h) I wonder how many of them will be
> > > needed for applications beyond the obvious ones that were listed.
> >
> > Well they only asked for seven of them. ;)
> >
> > I chatted with Ted about this yesterday, and ... some of the attributes
> > (like read only) imply that you'd want the linux server to enforce no
> > writing to the file; some like archive seem a little superfluous since
> > on linux you can compare cmtime from the backup against what's in the
> > file now; and still others (like hidden/system) might just be some dorky
> > thing that could be hidden in some xattr because a unix filesystem won't
> > care.
> >
> > And then there are other attrs like "integrity stream" where someone
> > with more experience with windows would have to tell me if fsverity
> > provides sufficient behaviors or not.
> >
> > But maybe we should start by plumbing one of those bits in?  I guess the
> > gross part is that implies an ondisk inode format change or (gross)
> > xattr lookups in the open path.
> >
> 
> We have talked about some of these missing flags in the past, but the
> obvious ones that would be helpful i (e.g. is used in other operating
> systems when view directories in the equivalent of the "Files" GUI is
> checking FILE_ATTRIBUTE_OFFLINE to determine whether to query icons,
> and additional metadata for files).  In the past Unix used to have
> various ways to determine this, but it is fairly common for files to
> be tiered (where the data is in very slow storage offline - so should
> only be opened and read by apps that really need to - not things like
> GUIs browsing lists of files) so that attribute could be helpful.
> 
> The other two obvious ones (missing in Linux but that some other OS
> have filesystems which support) discussed before were
> FILE_ATTRIBUTE_INTEGRITY_STREAM which could be set for files that need
> stronger data integrity guarantees (if a filesystem allows files to be
> marked for stronger data integrity guarantees) , and
> FILE_ATTRIBUTE_NO_SCRUB_DATA that indicates integrity checks can be
> skipped for this particular file.
> -- 
> Thanks,
> 
> Steve

Thank you for information about integrity stream and these new things
around. I have not included them into my initial list because I have not
used them yet. That it why I listed only seven. But as I wrote in the
other email, whatever API is chosen, it should be prepared for extending
and integrity stream sounds like something could be included there.

  reply	other threads:[~2025-01-17 17:58 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-27 12:15 Immutable vs read-only for Windows compatibility Pali Rohár
2025-01-02 14:37 ` Jan Kara
2025-01-02 15:52   ` Chuck Lever
2025-01-02 18:12     ` Pali Rohár
2025-01-04  8:52     ` Christian Brauner
2025-01-04 11:12       ` Pali Rohár
2025-01-04 15:30       ` Chuck Lever
2025-01-14 21:10         ` Pali Rohár
2025-01-14 21:44           ` Chuck Lever
2025-01-14 21:53             ` Pali Rohár
2025-01-14 23:21               ` Darrick J. Wong
2025-01-14 23:29               ` ronnie sahlberg
2025-01-14 23:55                 ` Pali Rohár
2025-01-14 23:59                   ` Darrick J. Wong
2025-01-15  6:26                     ` Maciej W. Rozycki
2025-01-17 16:53                     ` Amir Goldstein
2025-01-17 17:39                       ` Darrick J. Wong
2025-01-17 17:51                         ` Steve French
2025-01-17 17:57                           ` Pali Rohár [this message]
2025-01-17 18:46                         ` Amir Goldstein
2025-01-17 18:59                           ` Pali Rohár
2025-02-02 15:23                             ` Pali Rohár
2025-02-03 21:59                               ` Amir Goldstein
2025-02-03 22:19                                 ` Pali Rohár
2025-02-03 23:02                                   ` Amir Goldstein
2025-02-03 23:34                                     ` Pali Rohár
2025-02-04 11:54                                       ` Amir Goldstein
2025-02-04 21:26                                         ` Pali Rohár
2025-02-05 16:33                                           ` Amir Goldstein
2025-02-05 18:16                                             ` Pali Rohár
2025-02-05 19:04                                               ` Pali Rohár
2025-02-05 21:47                                                 ` Amir Goldstein
2025-02-05 22:01                                               ` Amir Goldstein
2025-02-04 21:32                                 ` Pali Rohár
2025-02-15 23:39                               ` Pali Rohár
2025-01-17 20:21                           ` Darrick J. Wong
2025-01-22  6:05                             ` Christoph Hellwig
2025-01-17 17:52                       ` Pali Rohár
2025-01-14 23:32             ` Dave Chinner
2025-01-14 23:42               ` ronnie sahlberg
2025-01-15  0:16                 ` Pali Rohár
2025-01-02 17:59   ` 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=20250117175755.lctf5ezhhtdznt6m@pali \
    --to=pali@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=sfrench@samba.org \
    --cc=smfrench@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).