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.8-rc2
Date: Wed, 2 Jan 2013 10:42:22 -0800 [thread overview]
Message-ID: <20130102184221.GB20946@boyd> (raw)
[-- Attachment #1: Type: text/plain, Size: 1259 bytes --]
Hi Linus,
The following changes since commit 0e4a43ed08e2f44aa7b96aa95d0a540d675483e1:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-3.0-fixes (2012-11-07 13:38:56 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-3.8-rc2-fixes
for you to fetch changes up to 37028758f92d0a3eb74bcfbecf6bc477072e9e28:
fs/ecryptfs/crypto.c: make ecryptfs_encode_for_filename() static (2012-12-18 10:10:13 -0600)
----------------------------------------------------------------
Two self-explanatory fixes and a third patch which improves performance. When
overwriting a full page in the eCryptfs page cache, skip reading in and
decrypting the corresponding lower page.
----------------------------------------------------------------
Cong Ding (1):
fs/ecryptfs/crypto.c: make ecryptfs_encode_for_filename() static
Li Wang (1):
eCryptfs: Avoid unnecessary disk read and data decryption during writing
Wei Yongjun (1):
eCryptfs: fix to use list_for_each_entry_safe() when delete items
fs/ecryptfs/crypto.c | 2 +-
fs/ecryptfs/kthread.c | 6 +++---
fs/ecryptfs/mmap.c | 12 ++++++++++--
3 files changed, 14 insertions(+), 6 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2013-01-02 18:42 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=20130102184221.GB20946@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).