From: Eric Biggers <ebiggers@kernel.org>
To: stable@vger.kernel.org
Cc: linux-fscrypt@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-mtd@lists.infradead.org
Subject: [PATCH 5.4 0/4] fscrypt: prevent creating duplicate encrypted filenames
Date: Mon, 28 Dec 2020 10:54:29 -0800 [thread overview]
Message-ID: <20201228185433.61129-1-ebiggers@kernel.org> (raw)
Backport four commits from v5.11-rc1. I resolved a conflict in the
first one. The rest are clean cherry-picks which didn't get picked up
yet because they depend on the first one.
Eric Biggers (4):
fscrypt: add fscrypt_is_nokey_name()
ext4: prevent creating duplicate encrypted filenames
f2fs: prevent creating duplicate encrypted filenames
ubifs: prevent creating duplicate encrypted filenames
fs/crypto/hooks.c | 10 +++++-----
fs/ext4/namei.c | 3 +++
fs/f2fs/f2fs.h | 2 ++
fs/ubifs/dir.c | 17 +++++++++++++----
include/linux/fscrypt.h | 34 ++++++++++++++++++++++++++++++++++
5 files changed, 57 insertions(+), 9 deletions(-)
--
2.29.2
next reply other threads:[~2020-12-28 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 18:54 Eric Biggers [this message]
2020-12-28 18:54 ` [PATCH 5.4 1/4] fscrypt: add fscrypt_is_nokey_name() Eric Biggers
2020-12-28 18:54 ` [PATCH 5.4 2/4] ext4: prevent creating duplicate encrypted filenames Eric Biggers
2020-12-28 18:54 ` [PATCH 5.4 3/4] f2fs: " Eric Biggers
2020-12-28 18:54 ` [PATCH 5.4 4/4] ubifs: " Eric Biggers
2020-12-30 15:39 ` [PATCH 5.4 0/4] fscrypt: " Greg KH
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=20201228185433.61129-1-ebiggers@kernel.org \
--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 \
--cc=stable@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).