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.7-rc7
Date: Fri, 8 Jul 2016 10:49:40 -0500 [thread overview]
Message-ID: <20160708154918.GA5442@boyd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]
Hi Linus,
The following changes since commit 33688abb2802ff3a230bd2441f765477b94cc89e:
Linux 4.7-rc4 (2016-06-19 21:30:02 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-4.7-rc7-fixes
for you to fetch changes up to f0fe970df3838c202ef6c07a4c2b36838ef0a88b:
ecryptfs: don't allow mmap when the lower fs doesn't support it (2016-07-08 10:35:28 -0500)
----------------------------------------------------------------
eCryptfs fixes for 4.7-rc7:
- Provide a more concise fix for CVE-2016-1583
+ Additionally fixes linux-stable regressions caused by the cherry-picking of
the original fix
- Some very minor changes that have queued up
+ Fix typos in code comments
+ Remove unnecessary check for NULL before destroying kmem_cache
----------------------------------------------------------------
Chris J Arges (1):
ecryptfs: fix spelling mistakes
Jeff Mahoney (2):
Revert "ecryptfs: forbid opening files without mmap handler"
ecryptfs: don't allow mmap when the lower fs doesn't support it
Julia Lawall (1):
ecryptfs: drop null test before destroy functions
Wei Yuan (1):
eCryptfs: fix typos in comment
fs/ecryptfs/crypto.c | 8 ++++----
fs/ecryptfs/file.c | 19 ++++++++++++++++---
fs/ecryptfs/kthread.c | 13 ++-----------
fs/ecryptfs/main.c | 3 +--
4 files changed, 23 insertions(+), 20 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2016-07-08 15:49 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=20160708154918.GA5442@boyd \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.