diff options
| author | Tyler Hicks <tyhicks@linux.vnet.ibm.com> | 2011-07-26 19:47:08 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2011-08-04 21:58:39 -0700 |
| commit | efc977be4683816c39dfab38a34f68e07b78997e (patch) | |
| tree | f5e6296a2fffd89df762e4808339043411809c3a /fs/nfsd | |
| parent | a21353bae5e98fce18080a3691ef75ede61dd261 (diff) | |
| download | kernel_samsung_smdk4412-efc977be4683816c39dfab38a34f68e07b78997e.zip kernel_samsung_smdk4412-efc977be4683816c39dfab38a34f68e07b78997e.tar.gz kernel_samsung_smdk4412-efc977be4683816c39dfab38a34f68e07b78997e.tar.bz2 | |
eCryptfs: Unlock keys needed by ecryptfsd
commit b2987a5e05ec7a1af7ca42e5d5349d7a22753031 upstream.
Fixes a regression caused by b5695d04634fa4ccca7dcbc05bb4a66522f02e0b
Kernel keyring keys containing eCryptfs authentication tokens should not
be write locked when calling out to ecryptfsd to wrap and unwrap file
encryption keys. The eCryptfs kernel code can not hold the key's write
lock because ecryptfsd needs to request the key after receiving such a
request from the kernel.
Without this fix, all file opens and creates will timeout and fail when
using the eCryptfs PKI infrastructure. This is not an issue when using
passphrase-based mount keys, which is the most widely deployed eCryptfs
configuration.
Signed-off-by: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
Acked-by: Roberto Sassu <roberto.sassu@polito.it>
Tested-by: Roberto Sassu <roberto.sassu@polito.it>
Tested-by: Alexis Hafner1 <haf@zurich.ibm.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'fs/nfsd')
0 files changed, 0 insertions, 0 deletions