This 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, master has been updated
adcfeda xfs: remove a dmapi leftover
fbe5f28 xfs: writepage always has buffers
2c2da2d xfs: allow writeback from kswapd
ac20d66 xfs: remove incorrect log write optimization
a476c59 xfs: unregister inode shrinker before freeing filesystem structures
from 04d2da9c682ce2687db29136c60d8679e37e3b35 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit adcfeda23fee84212b235331cd71bf3d16dd137c
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Sat Jul 3 09:21:17 2010 +0000
xfs: remove a dmapi leftover
The open_exec file operation is only added by the external dmapi
patch.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Reviewed-by: Alex Elder <aelder@xxxxxxx>
Signed-off-by: Alex Elder <aelder@xxxxxxx>
commit fbe5f2875788e1039f02eeca615e6cb6d761c043
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon Jun 28 10:34:57 2010 -0400
xfs: writepage always has buffers
These days we always have buffers thanks to ->page_mkwrite. And we
already have an assert a few lines above tripping in case that was
not true due to a bug.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Alex Elder <aelder@xxxxxxx>
commit 2c2da2d1514dbc5ffcab05ceb8868d7f173f91f6
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon Jun 28 10:34:44 2010 -0400
xfs: allow writeback from kswapd
We only need disable I/O from direct or memcg reclaim.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Alex Elder <aelder@xxxxxxx>
commit ac20d66b86a5ace7650d41d83278f73340e824f4
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon Jun 28 10:34:34 2010 -0400
xfs: remove incorrect log write optimization
We do need a barrier for the first buffer of a split log write.
Otherwise we might incorrectly stamp the tail LSN into transactions
in the first part of the split write, or not flush data I/O before
updating the inode size.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Signed-off-by: Alex Elder <aelder@xxxxxxx>
commit a476c59ebb279d738718edc0e3fb76aab3687114
Author: Dave Chinner <dchinner@xxxxxxxxxx>
Date: Fri Jun 25 11:08:40 2010 +1000
xfs: unregister inode shrinker before freeing filesystem structures
Currently we don't remove the XFS mount from the shrinker list until
late in the unmount path. By this time, we have already torn down
the internals of the filesystem (e.g. the per-ag structures), and
hence if the shrinker is executed between the teardown and the
unregistering, the shrinker will get NULL per-ag structure pointers
and panic trying to dereference them.
Fix this by removing the xfs mount from the shrinker list before
tearing down it's internal structures.
Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx>
Reviewed-by: Eric Sandeen <sandeen@xxxxxxxxxx>
Signed-off-by: Alex Elder <aelder@xxxxxxx>
-----------------------------------------------------------------------
Summary of changes:
fs/xfs/linux-2.6/xfs_aops.c | 16 ++++------------
fs/xfs/linux-2.6/xfs_file.c | 3 ---
fs/xfs/linux-2.6/xfs_super.c | 6 +++++-
fs/xfs/xfs_log.c | 7 ++-----
4 files changed, 11 insertions(+), 21 deletions(-)
hooks/post-receive
--
XFS development tree
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
