diff options
| author | Jan Kara <jack@suse.cz> | 2013-03-13 12:57:08 +0100 |
|---|---|---|
| committer | Jan Kara <jack@suse.cz> | 2013-03-13 15:23:44 +0100 |
| commit | c288d2969627be7ffc90904ac8c6aae0295fbf9f (patch) | |
| tree | b8d9b4cafa65bf7b0c915b850c42e3df80dd5434 /fs/ext2/inode.c | |
| parent | reiserfs: Use kstrdup instead of kmalloc/strcpy (diff) | |
| download | linux-c288d2969627be7ffc90904ac8c6aae0295fbf9f.tar.xz linux-c288d2969627be7ffc90904ac8c6aae0295fbf9f.zip | |
ext2: Fix BUG_ON in evict() on inode deletion
Commit 8e3dffc6 introduced a regression where deleting inode with
large extended attributes leads to triggering
BUG_ON(inode->i_state != (I_FREEING | I_CLEAR))
in fs/inode.c:evict(). That happens because freeing of xattr block
dirtied the inode and it happened after clear_inode() has been called.
Fix the issue by moving removal of xattr block into ext2_evict_inode()
before clear_inode() call close to a place where data blocks are
truncated. That is also more logical place and removes surprising
requirement that ext2_free_blocks() mustn't dirty the inode.
Reported-by: Tyler Hicks <tyhicks@canonical.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to '')
| -rw-r--r-- | fs/ext2/inode.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/fs/ext2/inode.c b/fs/ext2/inode.c index c3881e56662e..fe60cc1117d8 100644 --- a/fs/ext2/inode.c +++ b/fs/ext2/inode.c @@ -34,6 +34,7 @@ #include "ext2.h" #include "acl.h" #include "xip.h" +#include "xattr.h" static int __ext2_write_inode(struct inode *inode, int do_sync); @@ -88,6 +89,7 @@ void ext2_evict_inode(struct inode * inode) inode->i_size = 0; if (inode->i_blocks) ext2_truncate_blocks(inode, 0); + ext2_xattr_delete_inode(inode); } invalidate_inode_buffers(inode); |