public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Chuck Lever <cel@kernel.org>
Cc: Al 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-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, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v5 01/16] fs: Add case sensitivity info to file_kattr
Date: Fri, 16 Jan 2026 08:28:37 -0800	[thread overview]
Message-ID: <20260116162837.GX15551@frogsfrogsfrogs> (raw)
In-Reply-To: <20260116144616.2098618-2-cel@kernel.org>

On Fri, Jan 16, 2026 at 09:46:00AM -0500, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
> 
> Enable upper layers such as NFSD to retrieve case sensitivity
> information from file systems by adding case_insensitive and
> case_nonpreserving boolean fields to struct file_kattr.
> 
> The case_insensitive and case_nonpreserving fields in struct
> file_kattr default to false (POSIX semantics: case-sensitive and
> case-preserving), allowing filesystems to set them only when
> behavior differs from the default.
> 
> Case sensitivity information is exported to userspace via the
> existing fa_xflags field using the new FS_XFLAG_CASEFOLD and
> FS_XFLAG_CASENONPRESERVING flags.
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
>  fs/file_attr.c           | 6 ++++++
>  include/linux/fileattr.h | 6 +++++-
>  include/uapi/linux/fs.h  | 2 ++
>  3 files changed, 13 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/file_attr.c b/fs/file_attr.c
> index 13cdb31a3e94..2f83f3c6a170 100644
> --- a/fs/file_attr.c
> +++ b/fs/file_attr.c
> @@ -84,6 +84,8 @@ int vfs_fileattr_get(struct dentry *dentry, struct file_kattr *fa)
>  	struct inode *inode = d_inode(dentry);
>  	int error;
>  
> +	memset(fa, 0, sizeof(*fa));

Hrm.  If you're going to memset the file_kattr here, then you might as
well remove the memset calls from fileattr_fill_*.  It's not great
that filesystems have to know that a "fill_xflags" function assigns to
more than just xflags.

> +
>  	if (!inode->i_op->fileattr_get)
>  		return -ENOIOCTLCMD;
>  
> @@ -106,6 +108,10 @@ static void fileattr_to_file_attr(const struct file_kattr *fa,
>  	fattr->fa_nextents = fa->fsx_nextents;
>  	fattr->fa_projid = fa->fsx_projid;
>  	fattr->fa_cowextsize = fa->fsx_cowextsize;
> +	if (fa->case_insensitive)
> +		fattr->fa_xflags |= FS_XFLAG_CASEFOLD;
> +	if (fa->case_nonpreserving)
> +		fattr->fa_xflags |= FS_XFLAG_CASENONPRESERVING;
>  }
>  
>  /**
> diff --git a/include/linux/fileattr.h b/include/linux/fileattr.h
> index f89dcfad3f8f..7f2e557255ce 100644
> --- a/include/linux/fileattr.h
> +++ b/include/linux/fileattr.h
> @@ -16,7 +16,8 @@
>  
>  /* Read-only inode flags */
>  #define FS_XFLAG_RDONLY_MASK \
> -	(FS_XFLAG_PREALLOC | FS_XFLAG_HASATTR)
> +	(FS_XFLAG_PREALLOC | FS_XFLAG_HASATTR | \
> +	 FS_XFLAG_CASEFOLD | FS_XFLAG_CASENONPRESERVING)
>  
>  /* Flags to indicate valid value of fsx_ fields */
>  #define FS_XFLAG_VALUES_MASK \
> @@ -51,6 +52,9 @@ struct file_kattr {
>  	/* selectors: */
>  	bool	flags_valid:1;
>  	bool	fsx_valid:1;
> +	/* case sensitivity behavior: */
> +	bool	case_insensitive:1;
> +	bool	case_nonpreserving:1;

Er... if you're encoding fs name handling qualities through FS_XFLAG_*,
then filesystems can set them in fsx_xflags directly.  No need for
separate bitfields here.

--D

>  };
>  
>  int copy_fsxattr_to_user(const struct file_kattr *fa, struct fsxattr __user *ufa);
> diff --git a/include/uapi/linux/fs.h b/include/uapi/linux/fs.h
> index 66ca526cf786..919148beaa8c 100644
> --- a/include/uapi/linux/fs.h
> +++ b/include/uapi/linux/fs.h
> @@ -253,6 +253,8 @@ struct file_attr {
>  #define FS_XFLAG_FILESTREAM	0x00004000	/* use filestream allocator */
>  #define FS_XFLAG_DAX		0x00008000	/* use DAX for IO */
>  #define FS_XFLAG_COWEXTSIZE	0x00010000	/* CoW extent size allocator hint */
> +#define FS_XFLAG_CASEFOLD	0x00020000	/* case-insensitive lookups */
> +#define FS_XFLAG_CASENONPRESERVING 0x00040000	/* case not preserved */
>  #define FS_XFLAG_HASATTR	0x80000000	/* no DIFLAG for this	*/
>  
>  /* the read-only stuff doesn't really belong here, but any other place is
> -- 
> 2.52.0
> 
> 

  reply	other threads:[~2026-01-16 16:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 14:45 [PATCH v5 00/16] Exposing case folding behavior Chuck Lever
2026-01-16 14:46 ` [PATCH v5 01/16] fs: Add case sensitivity info to file_kattr Chuck Lever
2026-01-16 16:28   ` Darrick J. Wong [this message]
2026-01-16 14:46 ` [PATCH v5 02/16] fat: Implement fileattr_get for case sensitivity Chuck Lever
2026-01-16 14:46 ` [PATCH v5 03/16] exfat: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 04/16] ntfs3: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 05/16] hfs: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 06/16] hfsplus: Report case sensitivity in fileattr_get Chuck Lever
2026-01-16 14:46 ` [PATCH v5 07/16] ext4: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 08/16] xfs: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 09/16] cifs: Implement fileattr_get for case sensitivity Chuck Lever
2026-01-16 14:46 ` [PATCH v5 10/16] nfs: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 11/16] f2fs: Add case sensitivity reporting to fileattr_get Chuck Lever
2026-01-16 14:46 ` [PATCH v5 12/16] vboxsf: Implement fileattr_get for case sensitivity Chuck Lever
2026-01-16 14:46 ` [PATCH v5 13/16] isofs: " Chuck Lever
2026-01-16 14:46 ` [PATCH v5 14/16] nfsd: Report export case-folding via NFSv3 PATHCONF Chuck Lever
2026-01-16 14:46 ` [PATCH v5 15/16] nfsd: Implement NFSv4 FATTR4_CASE_INSENSITIVE and FATTR4_CASE_PRESERVING Chuck Lever
2026-01-16 14:46 ` [PATCH v5 16/16] ksmbd: Report filesystem case sensitivity via FS_ATTRIBUTE_INFORMATION Chuck Lever

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=20260116162837.GX15551@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=adilger.kernel@dilger.ca \
    --cc=almaz.alexandrovich@paragon-software.com \
    --cc=anna@kernel.org \
    --cc=brauner@kernel.org \
    --cc=cel@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-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=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