From: Paolo Bonzini <pbonzini@redhat.com>
To: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, ecryptfs-devel@lists.launchpad.net
Subject: Re: [GIT PULL] eCryptfs updates for 2.6.39-rc1
Date: Wed, 30 Mar 2011 12:50:24 +0200 [thread overview]
Message-ID: <4D930AF0.2050708@redhat.com> (raw)
In-Reply-To: <20110328150205.GA9054@boyd.l.tihix.com>
On 03/28/2011 05:02 PM, Tyler Hicks wrote:
> Hi Linus,
>
> The eCryptfs patches for 2.6.39-rc1 are mainly fixes. Roberto's patches
> add key locking so keys aren't modified underneath us. Thieu's patch
> moves encryption to writepage so userspace isn't waiting on page
> encryption during each write(). My patches remove a wasteful
> encrypt/write operation during file creation and fix a missing page
> unlock in an error path.
>
> The following changes since commit 40471856f2e38e9bfa8d605295e8234421110dd6:
>
> Merge branch 'nfs-for-2.6.39' of git://git.linux-nfs.org/projects/trondmy/nfs-2.6 (2011-03-25 10:03:28 -0700)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/ecryptfs/ecryptfs-2.6.git for-linus
>
> Roberto Sassu (6):
> eCryptfs: ecryptfs_keyring_auth_tok_for_sig() bug fix
> eCryptfs: removed num_global_auth_toks from ecryptfs_mount_crypt_stat
> eCryptfs: modified size of keysig in the ecryptfs_key_sig structure
> eCryptfs: verify authentication tokens before their use
> eCryptfs: move ecryptfs_find_auth_tok_for_sig() call before mutex_lock
> eCryptfs: write lock requested keys
>
> Thieu Le (1):
> ecryptfs: modify write path to encrypt page in writepage
>
> Tyler Hicks (3):
> eCryptfs: Remove unnecessary grow_file() function
> eCryptfs: Remove ECRYPTFS_NEW_FILE crypt stat flag
> eCryptfs: Unlock page in write_begin error path
Is "eCryptfs: Handle failed metadata read in lookup" going into 2.6.39?
Paolo
next prev parent reply other threads:[~2011-03-30 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 15:02 [GIT PULL] eCryptfs updates for 2.6.39-rc1 Tyler Hicks
2011-03-30 10:50 ` Paolo Bonzini [this message]
2011-03-30 14:28 ` Tyler Hicks
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=4D930AF0.2050708@redhat.com \
--to=pbonzini@redhat.com \
--cc=ecryptfs-devel@lists.launchpad.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tyhicks@linux.vnet.ibm.com \
/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