| commit | 9b9f40e785724a265fb6027216fb2bd1e97894f7 | |
| author | Tim Gardner <tim.gardner@canonical.com> | |
| Thu, 12 Jan 2012 15:31:55 +0000 (12 16:31 +0100) | ||
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | |
| Fri, 3 Feb 2012 17:18:50 +0000 (3 09:18 -0800) | ||
| tree | 2744ada6cba7b709425bd2a6fba2b702fa43504a | treesnapshot (tar.gz zip) |
| parent | cdce30003c234575bbcfddb0980adc04b82408c7 | commitdiff |
ecryptfs: Improve metadata read failure logging
commit 30373dc0c87ffef68d5628e77d56ffb1fa22e1ee upstream.
Print inode on metadata read failure. The only real
way of dealing with metadata read failures is to delete
the underlying file system file. Having the inode
allows one to 'find . -inum INODE`.
[tyhicks@canonical.com: Removed some minor not-for-stable parts]
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
commit 30373dc0c87ffef68d5628e77d56ffb1fa22e1ee upstream.
Print inode on metadata read failure. The only real
way of dealing with metadata read failures is to delete
the underlying file system file. Having the inode
allows one to 'find . -inum INODE`.
[tyhicks@canonical.com: Removed some minor not-for-stable parts]
Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Tyler Hicks <tyhicks@canonical.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
| fs/ecryptfs/crypto.c | diffblobblamehistory |