From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-mtd@lists.infradead.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 0/5] fscrypt: prevent creating duplicate encrypted filenames
Date: Tue, 24 Nov 2020 15:28:14 -0800 [thread overview]
Message-ID: <X72XDv89kSPWCqTQ@sol.localdomain> (raw)
In-Reply-To: <20201118075609.120337-1-ebiggers@kernel.org>
On Tue, Nov 17, 2020 at 11:56:04PM -0800, Eric Biggers wrote:
> This series fixes a longstanding race condition where a duplicate
> filename can be created in an encrypted directory if a syscall that
> creates a new filename (e.g. open() or mkdir()) races with the
> directory's encryption key being added.
>
> To close this race, we need to prevent creating files if the dentry is
> still marked as a no-key name. I.e. we need to fail the ->create() (or
> other operation that creates a new filename) if the key wasn't available
> when doing the dentry lookup earlier in the syscall, even if the key was
> concurrently added between the dentry lookup and ->create().
>
> See patch 1 for a more detailed explanation.
>
> Patch 1 introduces a helper function required for the fix. Patches 2-4
> fix the bug on ext4, f2fs, and ubifs. Patch 5 is a cleanup.
>
> This fixes xfstest generic/595 on ubifs, but that test was hitting this
> bug only accidentally. I've also written a new xfstest which reproduces
> this bug on both ext4 and ubifs.
>
> Eric Biggers (5):
> fscrypt: add fscrypt_is_nokey_name()
> ext4: prevent creating duplicate encrypted filenames
> f2fs: prevent creating duplicate encrypted filenames
> ubifs: prevent creating duplicate encrypted filenames
> fscrypt: remove unnecessary calls to fscrypt_require_key()
>
> fs/crypto/hooks.c | 31 +++++++++++--------------------
> fs/ext4/namei.c | 3 +++
> fs/f2fs/f2fs.h | 2 ++
> fs/ubifs/dir.c | 17 +++++++++++++----
> include/linux/fscrypt.h | 37 +++++++++++++++++++++++++++++++++++--
> 5 files changed, 64 insertions(+), 26 deletions(-)
>
>
> base-commit: 3ceb6543e9cf6ed87cc1fbc6f23ca2db903564cd
All applied to fscrypt.git#master for 5.11.
I'd still appreciate acks for ext4, f2fs, and ubifs though.
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2020-11-24 23:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 7:56 [f2fs-dev] [PATCH 0/5] fscrypt: prevent creating duplicate encrypted filenames Eric Biggers
2020-11-18 7:56 ` [f2fs-dev] [PATCH 1/5] fscrypt: add fscrypt_is_nokey_name() Eric Biggers
2020-11-18 7:56 ` [f2fs-dev] [PATCH 2/5] ext4: prevent creating duplicate encrypted filenames Eric Biggers
2020-11-18 7:56 ` [f2fs-dev] [PATCH 3/5] f2fs: " Eric Biggers
2020-11-18 7:56 ` [f2fs-dev] [PATCH 4/5] ubifs: " Eric Biggers
2020-11-18 7:56 ` [f2fs-dev] [PATCH 5/5] fscrypt: remove unnecessary calls to fscrypt_require_key() Eric Biggers
2020-11-24 23:28 ` 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=X72XDv89kSPWCqTQ@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-fsdevel@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;
as well as URLs for NNTP newsgroup(s).