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 3.18
Date: Thu, 9 Oct 2014 16:23:48 -0500 [thread overview]
Message-ID: <20141009212310.GA13655@boyd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
Hi Linus,
The following changes since commit 319e2e3f63c348a9b66db4667efa73178e18b17d:
Linux 3.13-rc4 (2013-12-15 12:31:33 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-3.18-fixes
for you to fetch changes up to 0f9e2bf008a1b143973a01b52320eb66c20ac6ab:
ecryptfs: remove unneeded buggy code in ecryptfs_do_create() (2014-10-06 16:54:50 -0500)
----------------------------------------------------------------
Minor code cleanups and a fix for when eCryptfs metadata is stored in xattrs
----------------------------------------------------------------
Alexey Khoroshilov (1):
ecryptfs: remove unneeded buggy code in ecryptfs_do_create()
Chao Yu (1):
ecryptfs: avoid to access NULL pointer when write metadata in xattr
David Howells (1):
Use %pd in eCryptFS
Fabian Frederick (2):
fs/ecryptfs/messaging.c: remove null test before kfree
ecryptfs: remove unnecessary break after goto
Himangi Saraogi (1):
ecryptfs: Drop cast
Steven Rostedt (1):
ecryptfs: Remove unnecessary include of syscall.h in keystore.c
fs/ecryptfs/file.c | 4 ++--
fs/ecryptfs/inode.c | 25 ++++++++-----------------
fs/ecryptfs/keystore.c | 2 --
fs/ecryptfs/messaging.c | 3 +--
4 files changed, 11 insertions(+), 23 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2014-10-09 21:23 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=20141009212310.GA13655@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).