Linux userland API discussions
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: Cedric Blancher <cedric.blancher@gmail.com>,
	Christian Brauner <brauner@kernel.org>
Cc: Chuck Lever <chuck.lever@oracle.com>,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-xfs@vger.kernel.org, linux-cifs@vger.kernel.org,
	linux-nfs@vger.kernel.org, linux-api@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	hirofumi@mail.parknet.co.jp, linkinjeon@kernel.org,
	sj1557.seo@samsung.com, yuezhang.mo@sony.com,
	almaz.alexandrovich@paragon-software.com, slava@dubeyko.com,
	glaubitz@physik.fu-berlin.de, frank.li@vivo.com, tytso@mit.edu,
	adilger.kernel@dilger.ca, cem@kernel.org, sfrench@samba.org,
	pc@manguebit.org, ronniesahlberg@gmail.com,
	sprasad@microsoft.com, trondmy@kernel.org, anna@kernel.org,
	jaegeuk@kernel.org, chao@kernel.org, hansg@kernel.org,
	senozhatsky@chromium.org, "Darrick J. Wong" <djwong@kernel.org>,
	Roland Mainz <roland.mainz@nrubsig.org>,
	Steve French <stfrench@microsoft.com>
Subject: Re: [PATCH v14 00/15] Exposing case folding behavior
Date: Sat, 16 May 2026 10:48:09 -0400	[thread overview]
Message-ID: <bd45e387-cc11-4d19-8bd6-58a0251d7714@kernel.org> (raw)
In-Reply-To: <CALXu0UdsurG-ayuYViqs0HXOfgyDw8gpNC+f=5y59cuuSPUbBA@mail.gmail.com>

On 5/16/26 2:43 AM, Cedric Blancher wrote:
> On Mon, 11 May 2026 at 16:11, Christian Brauner <brauner@kernel.org> wrote:
>>
>> On Thu, 07 May 2026 04:52:53 -0400, Chuck Lever wrote:
>>> Christian, let's lock this one in. I will post subsequent changes
>>> as delta patches.
>>>
>>> Following on from:
>>>
>>> https://lore.kernel.org/linux-nfs/20251021-zypressen-bazillus-545a44af57fd@brauner/T/#m0ba197d75b7921d994cf284f3cef3a62abb11aaa
>>>
>>> [...]
>>
>> Applied to the vfs-7.2.exportfs branch of the vfs/vfs.git tree.
>> Patches in the vfs-7.2.exportfs branch should appear in linux-next soon.
> 
> @Chuck Lever Thank you!
> 
> Does that mean the support for case-insensitive filesystems will work
> with Linux 7.2?

I don't want to make claims with 100% certainty, but we expect this
series to get merged into 7.2. It's early days, so there are likely to
be bugs -- there is so much subtle behavior under the covers.


-- 
Chuck Lever

  reply	other threads:[~2026-05-16 14:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07  8:52 [PATCH v14 00/15] Exposing case folding behavior Chuck Lever
2026-05-07  8:52 ` [PATCH v14 01/15] fs: Move file_kattr initialization to callers Chuck Lever
2026-05-07  8:52 ` [PATCH v14 02/15] fs: Add case sensitivity flags to file_kattr Chuck Lever
2026-05-07  8:52 ` [PATCH v14 03/15] fat: Implement fileattr_get for case sensitivity Chuck Lever
2026-05-07  8:52 ` [PATCH v14 04/15] exfat: " Chuck Lever
2026-05-07  8:52 ` [PATCH v14 05/15] ntfs3: " Chuck Lever
2026-05-07  8:52 ` [PATCH v14 06/15] hfs: " Chuck Lever
2026-05-07  8:53 ` [PATCH v14 07/15] hfsplus: Report case sensitivity in fileattr_get Chuck Lever
2026-05-07  8:53 ` [PATCH v14 08/15] xfs: " Chuck Lever
2026-05-07  8:53 ` [PATCH v14 09/15] cifs: Implement fileattr_get for case sensitivity Chuck Lever
2026-05-07  8:53 ` [PATCH v14 10/15] nfs: " Chuck Lever
2026-05-07  8:53 ` [PATCH v14 11/15] vboxsf: " Chuck Lever
2026-05-07  8:53 ` [PATCH v14 12/15] isofs: " Chuck Lever
2026-05-07  8:53 ` [PATCH v14 13/15] nfsd: Report export case-folding via NFSv3 PATHCONF Chuck Lever
2026-05-07  8:53 ` [PATCH v14 14/15] nfsd: Implement NFSv4 FATTR4_CASE_INSENSITIVE and FATTR4_CASE_PRESERVING Chuck Lever
2026-05-07  8:53 ` [PATCH v14 15/15] ksmbd: Report filesystem case sensitivity via FS_ATTRIBUTE_INFORMATION Chuck Lever
2026-05-11 14:02 ` [PATCH v14 00/15] Exposing case folding behavior Christian Brauner
2026-05-11 14:07   ` Chuck Lever
2026-05-11 14:55     ` Christian Brauner
2026-05-16  6:43   ` Cedric Blancher
2026-05-16 14:48     ` Chuck Lever [this message]
2026-05-11 14:02 ` Christian Brauner
2026-05-11 14:55 ` Christian Brauner

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=bd45e387-cc11-4d19-8bd6-58a0251d7714@kernel.org \
    --to=cel@kernel.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=anna@kernel.org \
    --cc=brauner@kernel.org \
    --cc=cedric.blancher@gmail.com \
    --cc=cem@kernel.org \
    --cc=chao@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=djwong@kernel.org \
    --cc=frank.li@vivo.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=hansg@kernel.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jaegeuk@kernel.org \
    --cc=linkinjeon@kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=pc@manguebit.org \
    --cc=roland.mainz@nrubsig.org \
    --cc=ronniesahlberg@gmail.com \
    --cc=senozhatsky@chromium.org \
    --cc=sfrench@samba.org \
    --cc=sj1557.seo@samsung.com \
    --cc=slava@dubeyko.com \
    --cc=sprasad@microsoft.com \
    --cc=stfrench@microsoft.com \
    --cc=trondmy@kernel.org \
    --cc=tytso@mit.edu \
    --cc=yuezhang.mo@sony.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox