XFS development tree branch, xfs-fixes-for-3.14-rc3, created. xfs-for-linus-v3.14-rc1-2-12922-g3895e51
[email protected]
Tested-by Michael L. Semon Reviewed-by Christoph Hellwig Reviewed-by Brian Foster Reviewed-by Jie LiuThis is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "XFS development tree".
The branch, xfs-fixes-for-3.14-rc3 has been created
at 3895e51f6dbf6610519be070a3bede811f6ac4fb (commit)
- Log ----------------------------------------------------------------- commit 3895e51f6dbf6610519be070a3bede811f6ac4fb
Author: Dave Chinner <[email protected]> Date: Mon Feb 10 10:37:18 2014 +1100
xfs: ensure correct log item buffer alignment
On 32 bit platforms, the log item vector headers are not 64 bit aligned or sized. hence if we don't take care to align them correctly or pad the buffer appropriately for 8 byte alignment, we can end up with alignment issues when accessing the user buffer directly as a structure.
To solve this, simply pad the buffer headers to 64 bit offset so that the data section is always 8 byte aligned.
commit fe60a8a0919eeee862054137fed49f00b710d9cd
Author: Christoph Hellwig <[email protected]> Date: Mon Feb 10 10:35:22 2014 +1100
xfs: ensure correct timestamp updates from truncate
The VFS doesn't set the proper ATTR_CTIME and ATTR_MTIME values for truncate, so filesystems have to manually add them. The introduction of xfs_setattr_time accidentally broke this special case an caused a regression in generic/313. Fix this by removing the local mask variable in xfs_setattr_size so that we only have a single place to keep the attribute information.
-----------------------------------------------------------------------
hooks/post-receive
Signature · 6 lines
XFS development tree _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs