xfs: fix xfs_buf_ioerror_alert location reporting
Instead of passing __func__ to the error reporting function, let's use the return address builtins so that the messages actually tell you which higher level function called the buffer functions. This was previously true for the xfs_buf_read callers, but not for the xfs_trans_read_buf callers. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Reviewed-by: Dave Chinner <dchinner@redhat.com> Reviewed-by: Christoph Hellwig <hch@lst.de>
This commit is contained in:
@@ -803,7 +803,8 @@ xfs_buf_read_map(
|
||||
int nmaps,
|
||||
xfs_buf_flags_t flags,
|
||||
struct xfs_buf **bpp,
|
||||
const struct xfs_buf_ops *ops)
|
||||
const struct xfs_buf_ops *ops,
|
||||
xfs_failaddr_t fa)
|
||||
{
|
||||
struct xfs_buf *bp;
|
||||
int error;
|
||||
@@ -852,7 +853,7 @@ xfs_buf_read_map(
|
||||
*/
|
||||
if (error) {
|
||||
if (!XFS_FORCED_SHUTDOWN(target->bt_mount))
|
||||
xfs_buf_ioerror_alert(bp, __func__);
|
||||
xfs_buf_ioerror_alert(bp, fa);
|
||||
|
||||
bp->b_flags &= ~XBF_DONE;
|
||||
xfs_buf_stale(bp);
|
||||
@@ -885,7 +886,8 @@ xfs_buf_readahead_map(
|
||||
return;
|
||||
|
||||
xfs_buf_read_map(target, map, nmaps,
|
||||
XBF_TRYLOCK | XBF_ASYNC | XBF_READ_AHEAD, &bp, ops);
|
||||
XBF_TRYLOCK | XBF_ASYNC | XBF_READ_AHEAD, &bp, ops,
|
||||
__this_address);
|
||||
}
|
||||
|
||||
/*
|
||||
@@ -1234,10 +1236,10 @@ __xfs_buf_ioerror(
|
||||
void
|
||||
xfs_buf_ioerror_alert(
|
||||
struct xfs_buf *bp,
|
||||
const char *func)
|
||||
xfs_failaddr_t func)
|
||||
{
|
||||
xfs_alert(bp->b_mount,
|
||||
"metadata I/O error in \"%s\" at daddr 0x%llx len %d error %d",
|
||||
"metadata I/O error in \"%pS\" at daddr 0x%llx len %d error %d",
|
||||
func, (uint64_t)XFS_BUF_ADDR(bp), bp->b_length,
|
||||
-bp->b_error);
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user