summaryrefslogtreecommitdiffstats
path: root/fs/affs
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2014-05-22 05:36:07 +0900
committerLinus Torvalds <torvalds@linux-foundation.org>2014-05-22 05:36:07 +0900
commit5e9d9fc4edd3f591e3cf76dd19a8b2a9c8d5cee1 (patch)
tree8601feb292b7037e140fee9f46b1354e0852f7f8 /fs/affs
parent80932ec1c0da97674417b35ac5aec31732993d8d (diff)
parentee4eec478be4677b93775d17bc079efb5922b276 (diff)
downloadtalos-op-linux-5e9d9fc4edd3f591e3cf76dd19a8b2a9c8d5cee1.tar.gz
talos-op-linux-5e9d9fc4edd3f591e3cf76dd19a8b2a9c8d5cee1.zip
Merge tag 'xfs-for-linus-3.15-rc6' of git://oss.sgi.com/xfs/xfs
Pull xfs fixes from Dave Chinner: "Code inspection of the XFS error number sign translations found a bunch of issues, including returning incorrectly signed errors for some data integrity operations. These leak to userspace and result in applications not getting the errors correctly reported. Hence they need fixing sooner rather than later. A couple of the bugs are in data integrity operations, a couple more are in the new COLLAPSE_RANGE code. One of these came in through a recent ext4 merge and so I had to update the base tree to 3.15-rc5 before fixing the issues" * tag 'xfs-for-linus-3.15-rc6' of git://oss.sgi.com/xfs/xfs: xfs: list_lru_init returns a negative error xfs: negate xfs_icsb_init_counters error value xfs: negate mount workqueue init error value xfs: fix wrong err sign on xfs_set_acl() xfs: fix wrong errno from xfs_initxattrs xfs: correct error sign on COLLAPSE_RANGE errors xfs: xfs_commit_metadata returns wrong errno xfs: fix incorrect error sign in xfs_file_aio_read xfs: xfs_dir_fsync() returns positive errno
Diffstat (limited to 'fs/affs')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud