From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: "Amir Goldstein" <amir73il@gmail.com>,
"Pali Rohár" <pali@kernel.org>,
"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>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: Immutable vs read-only for Windows compatibility
Date: Tue, 21 Jan 2025 22:05:40 -0800 [thread overview]
Message-ID: <Z5CKtOwB8ZsbX4N4@infradead.org> (raw)
In-Reply-To: <20250117202112.GH3561231@frogsfrogsfrogs>
On Fri, Jan 17, 2025 at 12:21:12PM -0800, Darrick J. Wong wrote:
> > Full disclosure - I have an out of tree xfs patch that implements
> > ioctls XFS_IOC_[GS]ETDOSATTRAT and stashes these
> > attributes in the unused di_dmevmask space.
>
> [cc linux-xfs]
>
> Urrrrk, please don't fork the xfs ondisk format!
Yeah, adding your own bits to any file system on-disk format is a huge
no-go.
next prev parent reply other threads:[~2025-01-22 6:05 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
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 [this message]
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=Z5CKtOwB8ZsbX4N4@infradead.org \
--to=hch@infradead.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=linux-xfs@vger.kernel.org \
--cc=pali@kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=sfrench@samba.org \
--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).