diff options
| author | Tyler Hicks <tyhicks@linux.vnet.ibm.com> | 2010-02-11 07:10:38 -0600 |
|---|---|---|
| committer | Tyler Hicks <tyhicks@linux.vnet.ibm.com> | 2010-03-23 12:29:49 -0500 |
| commit | 157f1071354db1aed885816094888e0e257c9d0a (patch) | |
| tree | 711d00d7dce97f846342db0a27b4a61c6b1966a4 /fs/exec.c | |
| parent | 220bf991b0366cc50a94feede3d7341fa5710ee4 (diff) | |
| download | kernel_samsung_tuna-157f1071354db1aed885816094888e0e257c9d0a.zip kernel_samsung_tuna-157f1071354db1aed885816094888e0e257c9d0a.tar.gz kernel_samsung_tuna-157f1071354db1aed885816094888e0e257c9d0a.tar.bz2 | |
eCryptfs: Fix metadata in xattr feature regression
Fixes regression in 8faece5f906725c10e7a1f6caf84452abadbdc7b
When using the ecryptfs_xattr_metadata mount option, eCryptfs stores the
metadata (normally stored at the front of the file) in the user.ecryptfs
xattr. This causes ecryptfs_crypt_stat.num_header_bytes_at_front to be
0, since there is no header data at the front of the file. This results
in too much memory being requested and ENOMEM being returned from
ecryptfs_write_metadata().
This patch fixes the problem by using the num_header_bytes_at_front
variable for specifying the max size of the metadata, despite whether it
is stored in the header or xattr.
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Tyler Hicks <tyhicks@linux.vnet.ibm.com>
Diffstat (limited to 'fs/exec.c')
0 files changed, 0 insertions, 0 deletions