From: Eric Biggers <ebiggers3@gmail.com>
To: linux-fscrypt@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org,
"Theodore Y . Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>,
Richard Weinberger <richard@nod.at>,
Michael Halcrow <mhalcrow@google.com>,
Eric Biggers <ebiggers@google.com>
Subject: [PATCH 0/4] fscrypt context consistency check fixes
Date: Fri, 7 Apr 2017 10:58:36 -0700 [thread overview]
Message-ID: <20170407175840.95740-1-ebiggers3@gmail.com> (raw)
From: Eric Biggers <ebiggers@google.com>
This patchset fixes fscrypt_has_permitted_context() to correctly handle cases
where one or both encryption keys are missing, then updates the ->lookup()
methods for ext4, f2fs, and ubifs to be consistent in how they handle the
encryption context consistency check.
Eric Biggers (4):
fscrypt: fix context consistency check when key(s) unavailable
ext4: remove "nokey" check from ext4_lookup()
f2fs: sync f2fs_lookup() with ext4_lookup()
ubifs: check for consistent encryption contexts in ubifs_lookup()
fs/crypto/policy.c | 87 ++++++++++++++++++++++++++++++++++++++++++------------
fs/ext4/namei.c | 9 +-----
fs/f2fs/namei.c | 7 +++--
fs/ubifs/dir.c | 11 +++++++
4 files changed, 84 insertions(+), 30 deletions(-)
--
2.12.2.715.g7642488e1d-goog
next reply other threads:[~2017-04-07 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 17:58 Eric Biggers [this message]
2017-04-07 17:58 ` [PATCH 1/4] fscrypt: fix context consistency check when key(s) unavailable Eric Biggers
2017-04-30 6:17 ` [1/4] " Theodore Ts'o
2017-05-02 17:36 ` Eric Biggers
2017-05-04 15:49 ` Theodore Ts'o
2017-04-07 17:58 ` [PATCH 2/4] ext4: remove "nokey" check from ext4_lookup() Eric Biggers
2017-04-30 6:17 ` [2/4] " Theodore Ts'o
2017-04-07 17:58 ` [PATCH 3/4] f2fs: sync f2fs_lookup() with ext4_lookup() Eric Biggers
2017-04-30 6:18 ` [3/4] " Theodore Ts'o
2017-04-07 17:58 ` [PATCH 4/4] ubifs: check for consistent encryption contexts in ubifs_lookup() Eric Biggers
2017-04-30 6:18 ` [4/4] " Theodore Ts'o
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=20170407175840.95740-1-ebiggers3@gmail.com \
--to=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mhalcrow@google.com \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
/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).