From: Chuck Lever <cel@kernel.org>
To: Jeff Layton <jlayton@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-nfs@vger.kernel.org
Cc: Chuck Lever <chuck.lever@oracle.com>,
Volker Lendecke <Volker.Lendecke@sernet.de>
Subject: Re: [RFC PATCH] fs: Plumb case sensitivity bits into statx
Date: Fri, 26 Sep 2025 09:05:21 -0400 [thread overview]
Message-ID: <39397920-3dc0-4295-b34d-67a298bf861b@kernel.org> (raw)
In-Reply-To: <ad767899918d26817e44f1af213a8dfdce26508a.camel@kernel.org>
On 9/26/25 3:00 AM, Jeff Layton wrote:
>> diff --git a/include/uapi/linux/stat.h b/include/uapi/linux/stat.h
>> index 1686861aae20..e929b30d64b6 100644
>> --- a/include/uapi/linux/stat.h
>> +++ b/include/uapi/linux/stat.h
>> @@ -219,6 +219,7 @@ struct statx {
>> #define STATX_SUBVOL 0x00008000U /* Want/got stx_subvol */
>> #define STATX_WRITE_ATOMIC 0x00010000U /* Want/got atomic_write_* fields */
>> #define STATX_DIO_READ_ALIGN 0x00020000U /* Want/got dio read alignment info */
>> +#define STATX_CASE_INFO 0x00040000U /* Want/got case folding info */
>>
>>
> Do you intend to expose this new attribute to userland? If not, then it
> should probably snuggle up next to STATX_CHANGE_COOKIE. If so, then you
> need to claim a field for it in struct statx, and populate it.
As I mentioned in the patch description, exposing to user space can be
done as a next step if we decide to pursue this proposal further. Yes,
that is something I have in mind.
--
Chuck Lever
prev parent reply other threads:[~2025-09-26 13:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 15:11 [RFC PATCH] fs: Plumb case sensitivity bits into statx Chuck Lever
2025-09-25 15:50 ` 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
2025-10-10 14:49 ` Darrick J. Wong
2025-10-10 19:06 ` Gabriel Krisman Bertazi
2025-10-03 17:19 ` Steve French
2025-09-26 4:20 ` Christoph Hellwig
2025-09-26 13:02 ` Chuck Lever
2025-09-26 10:00 ` Jeff Layton
2025-09-26 13:05 ` Chuck Lever [this message]
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=39397920-3dc0-4295-b34d-67a298bf861b@kernel.org \
--to=cel@kernel.org \
--cc=Volker.Lendecke@sernet.de \
--cc=chuck.lever@oracle.com \
--cc=jlayton@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 NNTP newsgroup(s).