diff options
author | Bryan Donlan <bdonlan@gmail.com> | 2009-06-30 11:41:24 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-06-30 18:56:00 -0700 |
commit | 4d6c13f87db12ae1ce35ea6a15688ac72419b133 (patch) | |
tree | 82af9604a6f22cd1fe720c56a7d8449f2acc03cd /mm | |
parent | 341c87bf346f57748230628c5ad6ee69219250e8 (diff) | |
download | kernel_goldelico_gta04-4d6c13f87db12ae1ce35ea6a15688ac72419b133.zip kernel_goldelico_gta04-4d6c13f87db12ae1ce35ea6a15688ac72419b133.tar.gz kernel_goldelico_gta04-4d6c13f87db12ae1ce35ea6a15688ac72419b133.tar.bz2 |
ext2: return -EIO not -ESTALE on directory traversal through deleted inode
ext2_iget() returns -ESTALE if invoked on a deleted inode, in order to
report errors to NFS properly. However, in ext[234]_lookup(), this
-ESTALE can be propagated to userspace if the filesystem is corrupted such
that a directory entry references a deleted inode. This leads to a
misleading error message - "Stale NFS file handle" - and confusion on the
part of the admin.
The bug can be easily reproduced by creating a new filesystem, making a
link to an unused inode using debugfs, then mounting and attempting to ls
-l said link.
This patch thus changes ext2_lookup to return -EIO if it receives -ESTALE
from ext2_iget(), as ext2 does for other filesystem metadata corruption;
and also invokes the appropriate ext*_error functions when this case is
detected.
Signed-off-by: Bryan Donlan <bdonlan@gmail.com>
Cc: <linux-ext4@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions