From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Daniel Rosenberg <drosen@google.com>,
Jeff Layton <jlayton@kernel.org>
Subject: Re: [PATCH 0/2] fscrypt: avoid ambiguous terms for "no-key name"
Date: Mon, 28 Sep 2020 14:55:20 -0700 [thread overview]
Message-ID: <20200928215520.GC1340@sol.localdomain> (raw)
In-Reply-To: <20200924042624.98439-1-ebiggers@kernel.org>
On Wed, Sep 23, 2020 at 09:26:22PM -0700, Eric Biggers wrote:
> This series fixes overloading of the terms "ciphertext name" and
> "encrypted name" to also sometimes mean "no-key name".
> The overloading of these terms has caused some confusion.
>
> No change in behavior.
>
> Eric Biggers (2):
> fscrypt: don't call no-key names "ciphertext names"
> fscrypt: rename DCACHE_ENCRYPTED_NAME to DCACHE_NOKEY_NAME
>
> fs/crypto/fname.c | 16 ++++++++--------
> fs/crypto/hooks.c | 13 ++++++-------
> fs/f2fs/dir.c | 2 +-
> include/linux/dcache.h | 2 +-
> include/linux/fscrypt.h | 25 ++++++++++++-------------
> 5 files changed, 28 insertions(+), 30 deletions(-)
Applied to fscrypt.git#master for 5.10.
- Eric
prev parent reply other threads:[~2020-09-28 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 4:26 [PATCH 0/2] fscrypt: avoid ambiguous terms for "no-key name" Eric Biggers
2020-09-24 4:26 ` [PATCH 1/2] fscrypt: don't call no-key names "ciphertext names" Eric Biggers
2020-09-24 4:26 ` [PATCH 2/2] fscrypt: rename DCACHE_ENCRYPTED_NAME to DCACHE_NOKEY_NAME Eric Biggers
2020-09-28 21:55 ` 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=20200928215520.GC1340@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=drosen@google.com \
--cc=jlayton@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).