[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YUlO1vmMXRaHHpTK@sol.localdomain>
Date: Mon, 20 Sep 2021 20:17:42 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: linux-fscrypt@...r.kernel.org
Cc: linux-ext4@...r.kernel.org, linux-mtd@...ts.infradead.org,
linux-f2fs-devel@...ts.sourceforge.net
Subject: Re: [PATCH] fscrypt: remove fscrypt_operations::max_namelen
On Thu, Sep 09, 2021 at 11:45:13AM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@...gle.com>
>
> The max_namelen field is unnecessary, as it is set to 255 (NAME_MAX) on
> all filesystems that support fscrypt (or plan to support fscrypt). For
> simplicity, just use NAME_MAX directly instead.
>
> Signed-off-by: Eric Biggers <ebiggers@...gle.com>
> ---
> fs/crypto/fname.c | 3 +--
> fs/ext4/super.c | 1 -
> fs/f2fs/super.c | 1 -
> fs/ubifs/crypto.c | 1 -
> include/linux/fscrypt.h | 3 ---
> 5 files changed, 1 insertion(+), 8 deletions(-)
Applied to fscrypt.git#master for 5.16.
- Eric
Powered by blists - more mailing lists