[XFS] Do not access buffers after dropping reference count
We should not access a buffer after dropping it's reference count otherwise we could race with another thread that releases the final reference count and frees the buffer causing us to access potentially unmapped memory. The bug this change fixes only occured on DEBUG XFS since the offending code was in an ASSERT. SGI-PV: 984429 SGI-Modid: xfs-linux-melb:xfs-kern:31715a Signed-off-by: Lachlan McIlroy <lachlan@sgi.com> Signed-off-by: David Chinner <david@fromorbit.com>
This commit is contained in:
parent
79071eb0b2
commit
3790689fa3
|
@ -838,6 +838,7 @@ xfs_buf_rele(
|
||||||
return;
|
return;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
ASSERT(atomic_read(&bp->b_hold) > 0);
|
||||||
if (atomic_dec_and_lock(&bp->b_hold, &hash->bh_lock)) {
|
if (atomic_dec_and_lock(&bp->b_hold, &hash->bh_lock)) {
|
||||||
if (bp->b_relse) {
|
if (bp->b_relse) {
|
||||||
atomic_inc(&bp->b_hold);
|
atomic_inc(&bp->b_hold);
|
||||||
|
@ -851,11 +852,6 @@ xfs_buf_rele(
|
||||||
spin_unlock(&hash->bh_lock);
|
spin_unlock(&hash->bh_lock);
|
||||||
xfs_buf_free(bp);
|
xfs_buf_free(bp);
|
||||||
}
|
}
|
||||||
} else {
|
|
||||||
/*
|
|
||||||
* Catch reference count leaks
|
|
||||||
*/
|
|
||||||
ASSERT(atomic_read(&bp->b_hold) >= 0);
|
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue