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, for-next has been updated
a2dcf5d xfs: do not call xfs_bdstrat_cb in xfs_buf_iodone_callbacks
08023d6 xfs: prevent recursion in xfs_buf_iorequest
eb71a12 xfs: don't defer metadata allocation to the workqueue
1f432a8 xfs: really fix the cursor leak in xfs_alloc_ag_vextent_near
from 9b73bd7b61f320ffe7bda0126592ccf836d7ef90 (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 a2dcf5df5f3813a44423d4a5026666e751ec00dd
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri Jul 13 02:24:10 2012 -0400
xfs: do not call xfs_bdstrat_cb in xfs_buf_iodone_callbacks
xfs_bdstrat_cb only adds a check for a shutdown filesystem over
xfs_buf_iorequest, but xfs_buf_iodone_callbacks just checked for a shut down
filesystem a little earlier. In addition the shutdown handling in
xfs_bdstrat_cb is not very suitable for this caller.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
Signed-off-by: Ben Myers <bpm@xxxxxxx>
commit 08023d6dbe840dc4271805a9ea376fcbdee9f744
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon Jul 2 06:00:04 2012 -0400
xfs: prevent recursion in xfs_buf_iorequest
If the b_iodone handler is run in calling context in xfs_buf_iorequest we
can run into a recursion where xfs_buf_iodone_callbacks keeps calling back
into xfs_buf_iorequest because an I/O error happened, which keeps calling
back into xfs_buf_iorequest. This chain will usually not take long
because the filesystem gets shut down because of log I/O errors, but even
over a short time it can cause stack overflows if run on the same context.
As a short term workaround make sure we always call the iodone handler in
workqueue context.
Signed-off-by: Christoph Hellwig <hch@xxxxxx>
Reviewed-by: Dave Chinner <dchinner@xxxxxxxxxx>
Signed-off-by: Ben Myers <bpm@xxxxxxx>
commit eb71a12e411fe065f8663e12a8d81d561f9502ee
Author: Dave Chinner <dchinner@xxxxxxxxxx>
Date: Thu Jul 12 07:40:43 2012 +1000
xfs: don't defer metadata allocation to the workqueue
Almost all metadata allocations come from shallow stack usage
situations. Avoid the overhead of switching the allocation to a
workqueue as we are not in danger of running out of stack when
making these allocations. Metadata allocations are already marked
through the args that are passed down, so this is trivial to do.
Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx>
Reported-by: Mel Gorman <mgorman@xxxxxxx>
Tested-by: Mel Gorman <mgorman@xxxxxxx>
Signed-off-by: Ben Myers <bpm@xxxxxxx>
commit 1f432a887e9a5a5c25be6ac72b5da13652c8bed3
Author: Dave Chinner <dchinner@xxxxxxxxxx>
Date: Thu Jul 12 07:40:42 2012 +1000
xfs: really fix the cursor leak in xfs_alloc_ag_vextent_near
The current cursor is reallocated when retrying the allocation, so
the existing cursor needs to be destroyed in both the restart and
the failure cases.
Signed-off-by: Dave Chinner <dchinner@xxxxxxxxxx>
Tested-by: Mike Snitzer <snitzer@xxxxxxxxxx>
Signed-off-by: Ben Myers <bpm@xxxxxxx>
-----------------------------------------------------------------------
Summary of changes:
fs/xfs/xfs_alloc.c | 19 +++++++++++++-----
fs/xfs/xfs_buf.c | 53 +++++++++++++++++++++----------------------------
fs/xfs/xfs_buf.h | 1 -
fs/xfs/xfs_buf_item.c | 2 +-
4 files changed, 38 insertions(+), 37 deletions(-)
hooks/post-receive
--
XFS development tree
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
