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.0-rc3
Date: Wed, 4 Mar 2015 16:14:34 -0600 [thread overview]
Message-ID: <20150304221433.GA25320@boyd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
Hi Linus,
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-4.0-rc3-fixes
for you to fetch changes up to 6d65261a09adaa374c05de807f73a144d783669e:
eCryptfs: don't pass fs-specific ioctl commands through (2015-03-03 02:03:56 -0600)
----------------------------------------------------------------
Fixes for proper ioctl handling and an untriggerable buffer overflow
- The eCryptfs ioctl handling functions should only pass known-good ioctl
commands to the lower filesystem
- A static checker found a potential buffer overflow. Upon inspection, it is
not triggerable due to input validation performed on the mount parameters.
----------------------------------------------------------------
Colin Ian King (1):
eCryptfs: ensure copy to crypt_stat->cipher does not overrun
Tyler Hicks (1):
eCryptfs: don't pass fs-specific ioctl commands through
fs/ecryptfs/ecryptfs_kernel.h | 4 ++--
fs/ecryptfs/file.c | 34 ++++++++++++++++++++++++++++++----
fs/ecryptfs/keystore.c | 2 +-
fs/ecryptfs/main.c | 2 +-
4 files changed, 34 insertions(+), 8 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2015-03-04 22:14 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=20150304221433.GA25320@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 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).