From: Tyler Hicks <tyhicks@canonical.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, ecryptfs@vger.kernel.org
Subject: [GIT PULL] eCryptfs fixes for 4.17-rc2
Date: Thu, 19 Apr 2018 16:10:29 +0000 [thread overview]
Message-ID: <20180419160750.GA16628@sec> (raw)
[-- Attachment #1: Type: text/plain, Size: 1318 bytes --]
Hi Linus,
The following changes since commit 3215b9d57a2c75c4305a3956ca303d7004485200:
Merge tag 'clk-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux (2018-03-20 17:44:27 -0700)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-4.17-rc2-fixes
for you to fetch changes up to e86281e700cca8a773f9a572fa406adf2784ba5c:
eCryptfs: don't pass up plaintext names when using filename encryption (2018-04-16 18:51:22 +0000)
----------------------------------------------------------------
Minor cleanups and a bug fix to completely ignore unencrypted filenames
in the lower filesystem when filename encryption is enabled at the
eCryptfs layer.
----------------------------------------------------------------
Colin Ian King (1):
ecryptfs: fix spelling mistake: "cadidate" -> "candidate"
Guenter Roeck (1):
ecryptfs: lookup: Don't check if mount_crypt_stat is NULL
Tyler Hicks (1):
eCryptfs: don't pass up plaintext names when using filename encryption
fs/ecryptfs/crypto.c | 41 ++++++++++++++++++++++++++++-------------
fs/ecryptfs/file.c | 21 ++++++++++++++++-----
fs/ecryptfs/inode.c | 3 +--
fs/ecryptfs/keystore.c | 2 +-
4 files changed, 46 insertions(+), 21 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2018-04-19 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180419160750.GA16628@sec \
--to=tyhicks@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=ecryptfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).