From: Gabriel Krisman Bertazi <krisman@suse.de>
To: "Pali Rohár" <pali@kernel.org>, "Amir Goldstein" <amir73il@gmail.com>
Cc: linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Theodore Ts'o <tytso@mit.edu>, Hugh Dickins <hughd@google.com>,
Daniel Tang <danielzgtg.opensource@gmail.com>,
linux-ext4@vger.kernel.org, Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org, linux-mm@kvack.org,
Chuck Lever <cel@kernel.org>
Subject: Re: [PATCH 4/4] ovl: Expose the filesystem encoding through sysfs
Date: Tue, 29 Sep 2026 11:35:49 -0400 [thread overview]
Message-ID: <87jyo4xe7e.fsf@mailhost.krisman.be> (raw)
In-Reply-To: <20260929144043.5rg4zf7uth333qke@pali>
Pali Rohár <pali@kernel.org> writes:
> On Tuesday 29 September 2026 16:15:04 Amir Goldstein wrote:
>> On Mon, Sep 28, 2026 at 11:32 PM Gabriel Krisman Bertazi
>> <krisman@suse.de> wrote:
>> >
>> > This patch reproduces the same interface from ext4/f2fs to have feature
>> > parity, so users don't need to rely on parsing dmesg or trying +F on a
>> > temporary directory just to check for support. Note there is no
>> > encoding_flags file, as none are supported by ovl.
>> >
>>
>> Gabriel,
>>
>> I am not ok with this API.
>> It is wrong in several ways.
>> It is not generic, we have already file_getattr() to get casefold status.
>> There was a suggestion by Pali [1] to get the supported xflags - statx style,
>> which can be a way to say if a fs could return FS_XFLAG_CASEFOLD.
>
> Yea, sorry for that. I have not finished it, I did not have time. But I
> would like to address this as this is something was was asked more
> times...
please cc me when sending it.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2026-09-29 15:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 21:31 [PATCH 0/4] Expose encoding information of volumes Gabriel Krisman Bertazi
2026-09-28 21:31 ` [PATCH 1/4] shmem: Report casefold setting in mount options Gabriel Krisman Bertazi
2026-09-28 21:39 ` sashiko-bot
2026-09-29 14:00 ` Mohammed EL Kadiri
2026-09-29 15:17 ` Gabriel Krisman Bertazi
2026-09-28 21:31 ` [PATCH 2/4] ext4: Expose the filesystem encoding through sysfs Gabriel Krisman Bertazi
2026-09-28 21:45 ` sashiko-bot
2026-09-29 0:18 ` Gabriel Krisman Bertazi
2026-09-28 21:31 ` [PATCH 3/4] ovl: Add /sys/fs/overlay plumbing Gabriel Krisman Bertazi
2026-09-28 21:38 ` sashiko-bot
2026-09-28 21:31 ` [PATCH 4/4] ovl: Expose the filesystem encoding through sysfs Gabriel Krisman Bertazi
2026-09-28 21:37 ` sashiko-bot
2026-09-29 14:15 ` Amir Goldstein
2026-09-29 14:40 ` Pali Rohár
2026-09-29 15:35 ` Gabriel Krisman Bertazi [this message]
2026-09-29 15:35 ` Gabriel Krisman Bertazi
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=87jyo4xe7e.fsf@mailhost.krisman.be \
--to=krisman@suse.de \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=cel@kernel.org \
--cc=danielzgtg.opensource@gmail.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=pali@kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.