linux.git/fs, branch v3.13-rc8

Merge tag 'xfs-for-linus-v3.13-rc8' of git://oss.sgi.com/xfs/xfs

2014-01-10T23:33:03+00:00

Pull xfs bugfixes from Ben Myers:
 "Here we have a bugfix for an off-by-one in the remote attribute
  verifier that results in a forced shutdown which you can hit with v5
  superblock by creating a 64k xattr, and a fix for a missing
  destroy_work_on_stack() in the allocation worker.

  It's a bit late, but they are both fairly straightforward"

* tag 'xfs-for-linus-v3.13-rc8' of git://oss.sgi.com/xfs/xfs:
  xfs: Calling destroy_work_on_stack() to pair with INIT_WORK_ONSTACK()
  xfs: fix off-by-one error in xfs_attr3_rmt_verify

xfs: Calling destroy_work_on_stack() to pair with INIT_WORK_ONSTACK()

2014-01-10T18:39:38+00:00

In case CONFIG_DEBUG_OBJECTS_WORK is defined, it is needed to
call destroy_work_on_stack() which frees the debug object to pair
with INIT_WORK_ONSTACK().

Signed-off-by: Liu, Chuansheng 
Reviewed-by: Ben Myers 
Signed-off-by: Ben Myers 

(cherry picked from commit 6f96b3063cdd473c68664a190524ed966ac0cd92)

xfs: fix off-by-one error in xfs_attr3_rmt_verify

2014-01-10T18:38:41+00:00

With CRC check is enabled, if trying to set an attributes value just
equal to the maximum size of XATTR_SIZE_MAX would cause the v3 remote
attr write verification procedure failure, which would yield the back
trace like below:


XFS (sda7): Internal error xfs_attr3_rmt_write_verify at line 191 of file fs/xfs/xfs_attr_remote.c

Call Trace:
[] dump_stack+0x45/0x56
[] xfs_error_report+0x3b/0x40 [xfs]
[] ? _xfs_buf_ioapply+0x6d/0x390 [xfs]
[] xfs_corruption_error+0x55/0x80 [xfs]
[] xfs_attr3_rmt_write_verify+0x14b/0x1a0 [xfs]
[] ? _xfs_buf_ioapply+0x6d/0x390 [xfs]
[] ? xfs_bdstrat_cb+0x55/0xb0 [xfs]
[] _xfs_buf_ioapply+0x6d/0x390 [xfs]
[] ? vm_map_ram+0x31a/0x460
[] ? wake_up_state+0x20/0x20
[] ? xfs_bdstrat_cb+0x55/0xb0 [xfs]
[] xfs_buf_iorequest+0x6b/0xc0 [xfs]
[] xfs_bdstrat_cb+0x55/0xb0 [xfs]
[] xfs_bwrite+0x46/0x80 [xfs]
[] xfs_attr_rmtval_set+0x334/0x490 [xfs]
[] xfs_attr_leaf_addname+0x24a/0x410 [xfs]
[] xfs_attr_set_int+0x223/0x470 [xfs]
[] xfs_attr_set+0x96/0xb0 [xfs]
[] xfs_xattr_set+0x42/0x70 [xfs]
[] generic_setxattr+0x62/0x80
[] __vfs_setxattr_noperm+0x63/0x1b0
[] ? evm_inode_setxattr+0xe/0x10
[] vfs_setxattr+0xb5/0xc0
[] setxattr+0x12e/0x1c0
[] ? final_putname+0x22/0x50
[] ? putname+0x2b/0x40
[] ? user_path_at_empty+0x5f/0x90
[] ? __sb_start_write+0x49/0xe0
[] ? vm_mmap_pgoff+0x99/0xc0
[] SyS_setxattr+0x8f/0xe0
[] system_call_fastpath+0x1a/0x1f

Tests:
    setfattr -n user.longxattr -v `perl -e 'print "A"x65536'` testfile

This patch fix it to check the remote EA size is greater than the
XATTR_SIZE_MAX rather than more than or equal to it, because it's
valid if the specified EA value size is equal to the limitation as
per VFS setxattr interface.

Signed-off-by: Jie Liu 
Reviewed-by: Mark Tinguely 
Signed-off-by: Ben Myers 

(cherry picked from commit 85dd0707f0cad26d60f2dc574d17a5ab948d10f7)

Merge tag 'ext4_for_linus_stable' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4

2014-01-07T00:22:42+00:00

Pull ext4 bugfix from Ted Ts'o:
 "Fix a regression introduced in v3.13-rc6"

* tag 'ext4_for_linus_stable' of http://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4:
  ext4: fix bigalloc regression

ext4: fix bigalloc regression

2014-01-06T19:00:23+00:00

Commit f5a44db5d2 introduced a regression on filesystems created with
the bigalloc feature (cluster size > blocksize).  It causes xfstests
generic/006 and /013 to fail with an unexpected JBD2 failure and
transaction abort that leaves the test file system in a read only state.
Other xfstests run on bigalloc file systems are likely to fail as well.

The cause is the accidental use of a cluster mask where a cluster
offset was needed in ext4_ext_map_blocks().

Signed-off-by: Eric Whitney

Merge branch 'akpm' (incoming from Andrew)

2014-01-02T22:40:38+00:00

Merge patches from Andrew Morton:
 "Ten fixes"

* emailed patches from Andrew Morton :
  epoll: do not take the nested ep->mtx on EPOLL_CTL_DEL
  sh: add EXPORT_SYMBOL(min_low_pfn) and EXPORT_SYMBOL(max_low_pfn) to sh_ksyms_32.c
  drivers/dma/ioat/dma.c: check DMA mapping error in ioat_dma_self_test()
  mm/memory-failure.c: transfer page count from head page to tail page after split thp
  MAINTAINERS: set up proper record for Xilinx Zynq
  mm: remove bogus warning in copy_huge_pmd()
  memcg: fix memcg_size() calculation
  mm: fix use-after-free in sys_remap_file_pages
  mm: munlock: fix deadlock in __munlock_pagevec()
  mm: munlock: fix a bug where THP tail page is encountered

epoll: do not take the nested ep->mtx on EPOLL_CTL_DEL

2014-01-02T22:40:30+00:00

The EPOLL_CTL_DEL path of epoll contains a classic, ab-ba deadlock.
That is, epoll_ctl(a, EPOLL_CTL_DEL, b, x), will deadlock with
epoll_ctl(b, EPOLL_CTL_DEL, a, x).  The deadlock was introduced with
commmit 67347fe4e632 ("epoll: do not take global 'epmutex' for simple
topologies").

The acquistion of the ep->mtx for the destination 'ep' was added such
that a concurrent EPOLL_CTL_ADD operation would see the correct state of
the ep (Specifically, the check for '!list_empty(&f.file->f_ep_links')

However, by simply not acquiring the lock, we do not serialize behind
the ep->mtx from the add path, and thus may perform a full path check
when if we had waited a little longer it may not have been necessary.
However, this is a transient state, and performing the full loop
checking in this case is not harmful.

The important point is that we wouldn't miss doing the full loop
checking when required, since EPOLL_CTL_ADD always locks any 'ep's that
its operating upon.  The reason we don't need to do lock ordering in the
add path, is that we are already are holding the global 'epmutex'
whenever we do the double lock.  Further, the original posting of this
patch, which was tested for the intended performance gains, did not
perform this additional locking.

Signed-off-by: Jason Baron 
Cc: Nathan Zimmer 
Cc: Eric Wong 
Cc: Nelson Elhage 
Cc: Al Viro 
Cc: Davide Libenzi 
Cc: "Paul E. McKenney" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Merge tag 'gfs2-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-3.0-fixes

2014-01-02T20:45:47+00:00

Pull GFS2 fixes from Steven Whitehouse:
 "Here is a set of small fixes for GFS2.  There is a fix to drop
  s_umount which is copied in from the core vfs, two patches relate to a
  hard to hit "use after free" and memory leak.  Two patches related to
  using DIO and buffered I/O on the same file to ensure correct
  operation in relation to glock state changes.  The final patch adds an
  RCU read lock to ensure correct locking on an error path"

* tag 'gfs2-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-3.0-fixes:
  GFS2: Fix unsafe dereference in dump_holder()
  GFS2: Wait for async DIO in glock state changes
  GFS2: Fix incorrect invalidation for DIO/buffered I/O
  GFS2: Fix slab memory leak in gfs2_bufdata
  GFS2: Fix use-after-free race when calling gfs2_remove_from_ail
  GFS2: don't hold s_umount over blkdev_put

GFS2: Fix unsafe dereference in dump_holder()

2014-01-02T12:18:04+00:00

GLOCK_BUG_ON() might call this function without RCU read lock. Make sure that
RCU read lock is held when using task_struct returned from pid_task().

Signed-off-by: Tetsuo Handa 
Signed-off-by: Steven Whitehouse

cifs: set FILE_CREATED

2013-12-27T21:14:45+00:00

Set FILE_CREATED on O_CREAT|O_EXCL.

cifs code didn't change during commit 116cc0225381415b96551f725455d067f63a76a0

Kernel bugzilla 66251

Signed-off-by: Shirish Pargaonkar 
Acked-by: Jeff Layton 
CC: Stable 
Signed-off-by: Steve French