kernel.git/fs/ext3/xattr.c, branch linux-3.14.y

ext2/3/4: use generic posix ACL infrastructure

2014-01-26T04:58:19Z

Signed-off-by: Christoph Hellwig Reviewed-by: Jan Kara Signed-off-by: Al Viro

Ext3: return ENOMEM rather than EIO if sb_getblk fails

2013-01-21T10:19:57Z

It will be better to use ENOMEM rather than EIO, because the only reason that sb_getblk fails is that allocation fails. Signed-off-by: Wang Shilong Signed-off-by: Jan Kara

Ext3: use unlikely to improve the efficiency of the kernel

2013-01-21T10:19:57Z

Because the function 'sb_getblk' seldomly fails to return NULL value,it will be better to use unlikely to check it. Signed-off-by: Wang Shilong Signed-off-by: Jan Kara

ext3: move headers to fs/ext3/

2012-03-31T20:03:16Z

Signed-off-by: Al Viro

ext3: Fix oops in ext3_try_to_allocate_with_rsv()

2011-06-25T15:29:52Z

Block allocation is called from two places: ext3_get_blocks_handle() and ext3_xattr_block_set(). These two callers are not necessarily synchronized because xattr code holds only xattr_sem and i_mutex, and ext3_get_blocks_handle() may hold only truncate_mutex when called from writepage() path. Block reservation code does not expect two concurrent allocations to happen to the same inode and thus assertions can be triggered or reservation structure corruption can occur. Fix the problem by taking truncate_mutex in xattr code to serialize allocations. CC: Sage Weil CC: stable@kernel.org Reported-by: Fyodor Ustinov Signed-off-by: Jan Kara

ext2,ext3,ext4: clarify comment for extN_xattr_set_handle

2011-01-10T17:10:30Z

Signed-off-by: Wang Sheng-Hui Signed-off-by: "Theodore Ts'o"

mbcache: Remove unused features

2010-08-09T20:48:45Z

The mbcache code was written to support a variable number of indexes, but all the existing users use exactly one index. Simplify to code to support only that case. There are also no users of the cache entry free operation, and none of the users keep extra data in cache entries. Remove those features as well. Signed-off-by: Andreas Gruenbacher Signed-off-by: Al Viro

ext3: constify xattr handlers

2010-05-21T22:31:19Z

Signed-off-by: Stephen Hemminger Signed-off-by: Al Viro

dquot: cleanup space allocation / freeing routines

2010-03-04T23:20:28Z

Get rid of the alloc_space, free_space, reserve_space, claim_space and release_rsv dquot operations - they are always called from the filesystem and if a filesystem really needs their own (which none currently does) it can just call into it's own routine directly. Move shared logic into the common __dquot_alloc_space, dquot_claim_space_nodirty and __dquot_free_space low-level methods, and rationalize the wrappers around it to move as much as possible code into the common block for CONFIG_QUOTA vs not. Also rename all these helpers to be named dquot_* instead of vfs_dq_*. Signed-off-by: Christoph Hellwig Signed-off-by: Jan Kara

ext3: Use bitops to read/modify EXT3_I(inode)->i_state

2010-03-04T23:20:20Z

At several places we modify EXT3_I(inode)->i_state without holding i_mutex (ext3_release_file, ext3_bmap, ext3_journalled_writepage, ext3_do_update_inode, ...). These modifications are racy and we can lose updates to i_state. So convert handling of i_state to use bitops which are atomic. Signed-off-by: Jan Kara