Linux EXT4 FS development
 help / color / mirror / Atom feed
From: "Chuck Lever" <cel@kernel.org>
To: "Mark Brown" <broonie@kernel.org>
Cc: "Alexander Viro" <viro@zeniv.linux.org.uk>,
	"Christian Brauner" <brauner@kernel.org>,
	"Jan Kara" <jack@suse.cz>,
	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,
	"OGAWA Hirofumi" <hirofumi@mail.parknet.co.jp>,
	"Namjae Jeon" <linkinjeon@kernel.org>,
	"Sungjong Seo" <sj1557.seo@samsung.com>,
	"Yuezhang Mo" <yuezhang.mo@sony.com>,
	almaz.alexandrovich@paragon-software.com,
	"Viacheslav Dubeyko" <slava@dubeyko.com>,
	"John Paul Adrian Glaubitz" <glaubitz@physik.fu-berlin.de>,
	frank.li@vivo.com, "Theodore Tso" <tytso@mit.edu>,
	adilger.kernel@dilger.ca, "Carlos Maiolino" <cem@kernel.org>,
	"Steve French" <sfrench@samba.org>,
	"Paulo Alcantara" <pc@manguebit.org>,
	"Ronnie Sahlberg" <ronniesahlberg@gmail.com>,
	"Shyam Prasad N" <sprasad@microsoft.com>,
	"Trond Myklebust" <trondmy@kernel.org>,
	"Anna Schumaker" <anna@kernel.org>,
	"Jaegeuk Kim" <jaegeuk@kernel.org>, "Chao Yu" <chao@kernel.org>,
	"Hans de Goede" <hansg@kernel.org>,
	senozhatsky@chromium.org, "Chuck Lever" <chuck.lever@oracle.com>,
	"Roland Mainz" <roland.mainz@nrubsig.org>
Subject: Re: [PATCH v14 03/15] fat: Implement fileattr_get for case sensitivity
Date: Wed, 20 May 2026 13:30:06 -0400	[thread overview]
Message-ID: <d2425b45-a37a-4cc9-8984-bed55ee54a32@app.fastmail.com> (raw)
In-Reply-To: <cdeaab82-06bf-47c1-8f6c-4e40dbec2344@sirena.org.uk>


On Wed, May 20, 2026, at 1:11 PM, Mark Brown wrote:
> On Wed, May 20, 2026 at 12:58:22PM -0400, Chuck Lever wrote:
>> The first option is the narrowest kernel-side change, and
>> matches what other minimal-fileattr filesystems do.
>
> That sounds like a good idea regardless of what we do with the test?

Yes, I have no objection to this approach, but it would be great to
hear from the vfat maintainers/contributors on this one before I
dig in.


-- 
Chuck Lever

  reply	other threads:[~2026-05-20 17:30 UTC|newest]

Thread overview: 31+ 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-20 14:31   ` Mark Brown
2026-05-20 14:39     ` Chuck Lever
2026-05-20 14:54       ` Mark Brown
2026-05-20 15:12         ` Chuck Lever
2026-05-20 15:19           ` Mark Brown
2026-05-20 16:58             ` Chuck Lever
2026-05-20 17:11               ` Mark Brown
2026-05-20 17:30                 ` Chuck Lever [this message]
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
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=d2425b45-a37a-4cc9-8984-bed55ee54a32@app.fastmail.com \
    --to=cel@kernel.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=anna@kernel.org \
    --cc=brauner@kernel.org \
    --cc=broonie@kernel.org \
    --cc=cem@kernel.org \
    --cc=chao@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=frank.li@vivo.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=hansg@kernel.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jack@suse.cz \
    --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=trondmy@kernel.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --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