From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, linux-mtd@lists.infradead.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] fscrypt: remove fscrypt_operations::max_namelen
Date: Mon, 20 Sep 2021 20:17:42 -0700 [thread overview]
Message-ID: <YUlO1vmMXRaHHpTK@sol.localdomain> (raw)
In-Reply-To: <20210909184513.139281-1-ebiggers@kernel.org>
On Thu, Sep 09, 2021 at 11:45:13AM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.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@google.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
prev parent reply other threads:[~2021-09-21 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 18:45 [PATCH] fscrypt: remove fscrypt_operations::max_namelen Eric Biggers
2021-09-21 3:17 ` Eric Biggers [this message]
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=YUlO1vmMXRaHHpTK@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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