Commit 93baa55a authored by Darrick J. Wong's avatar Darrick J. Wong

xfs: improve error message when we can't allocate memory for xfs_buf

If xfs_buf_get_map can't allocate enough memory for the buffer it's
trying to create, it'll cough up an error about not being able to
allocate "pagesn".  That's not particularly helpful (and if we're really
out of memory the message is very spammy) so change the message to tell
us how many pages were actually requested, and ratelimit it too.
Signed-off-by: default avatarDarrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: default avatarChristoph Hellwig <hch@lst.de>
parent d0c7feaf
...@@ -727,8 +727,9 @@ xfs_buf_get_map( ...@@ -727,8 +727,9 @@ xfs_buf_get_map(
if (!bp->b_addr) { if (!bp->b_addr) {
error = _xfs_buf_map_pages(bp, flags); error = _xfs_buf_map_pages(bp, flags);
if (unlikely(error)) { if (unlikely(error)) {
xfs_warn(target->bt_mount, xfs_warn_ratelimited(target->bt_mount,
"%s: failed to map pagesn", __func__); "%s: failed to map %u pages", __func__,
bp->b_page_count);
xfs_buf_relse(bp); xfs_buf_relse(bp);
return error; return error;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment