kernel/git/next/linux-next.git/fs/ext3/xattr.c, branch master

fs: Remove ext3 filesystem driver

2015-07-23T18:59:40+00:00

The functionality of ext3 is fully supported by ext4 driver. Major distributions (SUSE, RedHat) already use ext4 driver to handle ext3 filesystems for quite some time. There is some ugliness in mm resulting from jbd cleaning buffers in a dirty page without cleaning page dirty bit and also support for buffer bouncing in the block layer when stable pages are required is there only because of jbd. So let's remove the ext3 driver. This saves us some 28k lines of duplicated code. Acked-by: Theodore Ts'o Signed-off-by: Jan Kara

Merge branch 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs

2015-04-27T00:22:07+00:00

Pull fourth vfs update from Al Viro: "d_inode() annotations from David Howells (sat in for-next since before the beginning of merge window) + four assorted fixes" * 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs: RCU pathwalk breakage when running into a symlink overmounting something fix I_DIO_WAKEUP definition direct-io: only inc/dec inode->i_dio_count for file systems fs/9p: fix readdir() VFS: assorted d_backing_inode() annotations VFS: fs/inode.c helpers: d_inode() annotations VFS: fs/cachefiles: d_backing_inode() annotations VFS: fs library helpers: d_inode() annotations VFS: assorted weird filesystems: d_inode() annotations VFS: normal filesystems (and lustre): d_inode() annotations VFS: security/: d_inode() annotations VFS: security/: d_backing_inode() annotations VFS: net/: d_inode() annotations VFS: net/unix: d_backing_inode() annotations VFS: kernel/: d_inode() annotations VFS: audit: d_backing_inode() annotations VFS: Fix up some ->d_inode accesses in the chelsio driver VFS: Cachefiles should perform fs modifications on the top layer only VFS: AF_UNIX sockets should call mknod on the top layer only

VFS: normal filesystems (and lustre): d_inode() annotations

2015-04-15T19:06:57+00:00

that's the bulk of filesystem drivers dealing with inodes of their own Signed-off-by: David Howells Signed-off-by: Al Viro

ext3: Remove useless condition in if statement.

2015-04-01T07:39:49+00:00

In this if statement, the previous condition is useless, the later one has covered it. Signed-off-by: Weiyuan Reviewed-by: Lukas Czerner Signed-off-by: Jan Kara

ext2/3/4: use generic posix ACL infrastructure

2014-01-26T04:58:19+00:00

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:57+00:00

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:57+00:00

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:16+00:00

Signed-off-by: Al Viro

ext3: Fix oops in ext3_try_to_allocate_with_rsv()

2011-06-25T15:29:52+00:00

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:30+00:00

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