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 4.19 0/5] backport some more fscrypt fixes to 4.19
Date: Sat, 31 Oct 2020 15:05:48 -0700 [thread overview]
Message-ID: <20201031220553.1085782-1-ebiggers@kernel.org> (raw)
Backport some fscrypt fixes from upstream 5.2 to 4.19-stable.
This is needed to get 'kvm-xfstests -c ext4,f2fs,ubifs -g encrypt' to
fully pass on 4.19-stable. Before, generic/397 and generic/429 failed
on UBIFS due to missing "fscrypt: fix race where ->lookup() marks
plaintext dentry as ciphertext".
This also fixes some bugs that aren't yet covered by the xfstests.
E.g., "fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing
directory" fixes a bug that caused real-world problems on Chrome OS.
Some relatively straightforward adjustments were needed to the patches,
mainly due to the refactoring of fscrypt.h that was done in 5.1.
Eric Biggers (5):
fscrypt: clean up and improve dentry revalidation
fscrypt: fix race allowing rename() and link() of ciphertext dentries
fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory
fscrypt: only set dentry_operations on ciphertext dentries
fscrypt: fix race where ->lookup() marks plaintext dentry as
ciphertext
fs/crypto/crypto.c | 58 +++++++++++++------------
fs/crypto/fname.c | 1 +
fs/crypto/hooks.c | 28 ++++++++----
fs/dcache.c | 15 +++++++
fs/ext4/ext4.h | 62 ++++++++++++++++++++-------
fs/ext4/namei.c | 76 ++++++++++++++++++++++-----------
fs/f2fs/namei.c | 17 +++++---
fs/ubifs/dir.c | 8 ++--
include/linux/dcache.h | 2 +-
include/linux/fscrypt.h | 30 +++++++------
include/linux/fscrypt_notsupp.h | 9 ++--
include/linux/fscrypt_supp.h | 6 ++-
12 files changed, 205 insertions(+), 107 deletions(-)
--
2.29.1
next reply other threads:[~2020-10-31 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 22:05 Eric Biggers [this message]
2020-10-31 22:05 ` [PATCH 4.19 1/5] fscrypt: clean up and improve dentry revalidation Eric Biggers
2020-10-31 22:05 ` [PATCH 4.19 2/5] fscrypt: fix race allowing rename() and link() of ciphertext dentries Eric Biggers
2020-10-31 22:05 ` [PATCH 4.19 3/5] fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory Eric Biggers
2020-10-31 22:05 ` [PATCH 4.19 4/5] fscrypt: only set dentry_operations on ciphertext dentries Eric Biggers
2020-10-31 22:05 ` [PATCH 4.19 5/5] fscrypt: fix race where ->lookup() marks plaintext dentry as ciphertext Eric Biggers
2020-11-01 10:39 ` [PATCH 4.19 0/5] backport some more fscrypt fixes to 4.19 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=20201031220553.1085782-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).