xfs: buffer ->bi_end_io function requires irq-safe lock
authorBrian Foster <bfoster@redhat.com>
Wed, 18 May 2016 00:56:41 +0000 (10:56 +1000)
committerDave Chinner <david@fromorbit.com>
Wed, 18 May 2016 00:56:41 +0000 (10:56 +1000)
commit9bdd9bd69b826875531bb1b2efb6aeb8d70e6f72
tree8cf9acecfa7280e4c3e43e116dc1f592665fa14b
parentf55532a0c0b8bb6148f4e07853b876ef73bc69ca
xfs: buffer ->bi_end_io function requires irq-safe lock

Reports have surfaced of a lockdep splat complaining about an
irq-safe -> irq-unsafe locking order in the xfs_buf_bio_end_io() bio
completion handler. This only occurs when I/O errors are present
because bp->b_lock is only acquired in this context to protect
setting an error on the buffer. The problem is that this lock can be
acquired with the (request_queue) q->queue_lock held. See
scsi_end_request() or ata_qc_schedule_eh(), for example.

Replace the locked test/set of b_io_error with a cmpxchg() call.
This eliminates the need for the lock and thus the lock ordering
problem goes away.

Signed-off-by: Brian Foster <bfoster@redhat.com>
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Dave Chinner <david@fromorbit.com>
fs/xfs/xfs_buf.c