summaryrefslogtreecommitdiffstats
path: root/fs/isofs
diff options
context:
space:
mode:
authorJan Kara <jack@suse.cz>2009-06-17 16:26:24 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2009-06-18 13:03:45 -0700
commitef43618a47179b41e7203a624f2c7445e7da488c (patch)
tree64d42f459e5086768e57d8e8e9bec8304b17c150 /fs/isofs
parent6f3f1cb21f08fbf757bbbbb0709ee515a7a7c6ad (diff)
downloadop-kernel-dev-ef43618a47179b41e7203a624f2c7445e7da488c.zip
op-kernel-dev-ef43618a47179b41e7203a624f2c7445e7da488c.tar.gz
ext3: make sure inode is deleted from orphan list after truncate
As Ted pointed out, it can happen that ext3_truncate() returns without removing inode from orphan list. This way we could in some rare cases (like when we get ENOMEM from an allocation in ext3_truncate called because of failed ext3_write_begin) leave the inode on orphan list and that triggers assertion failure on umount. So make ext3_truncate() always remove inode from in-memory orphan list. Cc: Theodore Ts'o <tytso@mit.edu> Signed-off-by: Jan Kara <jack@suse.cz> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/isofs')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud