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 updates for 3.11-rc1
Date: Wed, 10 Jul 2013 10:54:55 -0700 [thread overview]
Message-ID: <20130710175441.GA15884@boyd> (raw)
[-- Attachment #1: Type: text/plain, Size: 2007 bytes --]
Hi Linus,
The following changes since commit e8193ce572f0ddb8004acf976bba119f0abbe6ca:
Merge tag 'rdma-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband (2013-06-07 16:29:21 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git tags/ecryptfs-3.11-rc1-cleanup
for you to fetch changes up to cc18ec3c8f5dd735c1bff5da30fd33860c08a293:
Use ecryptfs_dentry_to_lower_path in a couple of places (2013-07-09 23:40:28 -0700)
----------------------------------------------------------------
Code cleanups and improved buffer handling during page crypto operations
- Remove redundant code by merging some encrypt and decrypt functions
- Get rid of a helper page allocation during page decryption by using in-place
decryption
- Better use of entire pages during page crypto operations
- Several code cleanups
----------------------------------------------------------------
Matthew Wilcox (1):
Use ecryptfs_dentry_to_lower_path in a couple of places
Thomas Meyer (1):
eCryptfs: Cocci spatch "memdup.spatch"
Tyler Hicks (10):
eCryptfs: Use entire helper page during page crypto operations
eCryptfs: Read/write entire page during page IO
eCryptfs: Simplify lower file offset calculation
eCryptfs: Accept one offset parameter in page offset crypto functions
eCryptfs: Decrypt pages in-place
eCryptfs: Combine encrypt_scatterlist() and decrypt_scatterlist()
eCryptfs: Combine page_offset crypto functions
eCryptfs: Merge ecryptfs_encrypt_extent() and ecryptfs_decrypt_extent()
eCryptfs: Collapse crypt_page_offset() into crypt_extent()
eCryptfs: Make extent and scatterlist crypt function parameters similar
fs/ecryptfs/crypto.c | 337 +++++++++++-------------------------------------
fs/ecryptfs/file.c | 7 +-
fs/ecryptfs/main.c | 7 +-
fs/ecryptfs/messaging.c | 3 +-
4 files changed, 85 insertions(+), 269 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
reply other threads:[~2013-07-10 17:55 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=20130710175441.GA15884@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.