From: Christian Brauner <brauner@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: Gabriel Krisman Bertazi <gabriel@krisman.be>,
Amir Goldstein <amir73il@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
Volker Lendecke <Volker.Lendecke@sernet.de>,
CIFS <linux-cifs@vger.kernel.org>
Subject: Re: [RFC PATCH] fs: Plumb case sensitivity bits into statx
Date: Tue, 21 Oct 2025 13:54:31 +0200 [thread overview]
Message-ID: <20251021-zypressen-bazillus-545a44af57fd@brauner> (raw)
In-Reply-To: <6b709bcc-d9bb-4227-8f84-96a67d86042b@kernel.org>
On Fri, Oct 10, 2025 at 08:43:33AM -0400, Chuck Lever wrote:
> On 10/10/25 7:11 AM, Christian Brauner wrote:
> >>> I'm not too fond of wasting statx() space for this. Couldn't this be
> >>> exposed via the new file_getattr() system call?:
> >> Do you mean exposing of unicode version and flags to userspace? If so,
> >> yes, for sure, it can be fit in file_get_attr. It was never exposed
> >> before, so there is no user expectation about it!
> > Imho it would fit better there than statx(). If this becomes really
> > super common than we can also later decide to additional expose it via
> > statx() but for now I think it'd be better to move this into the new
> > file_attr()* apis.
>
> Christian, I'm still not clear what you mean by "this". Do you mean only
> the unicode version? Or do you mean both the unicode version *and* the
> case sensitivity/preservation flags?
Sorry, my thought had been both would fit into file_getattr() if that's
feasible.
next prev parent reply other threads:[~2025-10-21 11:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250925151140.57548-1-cel@kernel.org>
2025-09-25 15:50 ` [RFC PATCH] fs: Plumb case sensitivity bits into statx Amir Goldstein
2025-10-03 15:24 ` Gabriel Krisman Bertazi
2025-10-03 15:34 ` Chuck Lever
2025-10-03 20:43 ` Gabriel Krisman Bertazi
2025-10-03 21:05 ` Chuck Lever
2025-10-03 21:11 ` ronnie sahlberg
2025-10-03 21:15 ` Gabriel Krisman Bertazi
2025-10-04 17:27 ` Chuck Lever
2025-10-06 11:19 ` Christian Brauner
2025-10-07 17:18 ` Gabriel Krisman Bertazi
2025-10-10 11:11 ` Christian Brauner
2025-10-10 12:43 ` Chuck Lever
2025-10-21 11:54 ` Christian Brauner [this message]
2025-10-10 14:49 ` Darrick J. Wong
2025-10-10 19:06 ` Gabriel Krisman Bertazi
2025-10-03 17:19 ` Steve French
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=20251021-zypressen-bazillus-545a44af57fd@brauner \
--to=brauner@kernel.org \
--cc=Volker.Lendecke@sernet.de \
--cc=amir73il@gmail.com \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=gabriel@krisman.be \
--cc=jlayton@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).