aboutsummaryrefslogtreecommitdiffstats
path: root/firmware
diff options
context:
space:
mode:
authorFUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>2009-04-03 19:28:06 +0900
committerJames Bottomley <James.Bottomley@HansenPartnership.com>2009-04-03 10:23:16 -0500
commit015640edb1f346e0b2eda703587c4cd1c310ec1d (patch)
treefd7016b45278d26eac055f1f613632b40832f46e /firmware
parent1beb6fa85ca9afaee109811a3f4a984232a32a4f (diff)
downloadmrst-s0i3-test-015640edb1f346e0b2eda703587c4cd1c310ec1d.tar.gz
mrst-s0i3-test-015640edb1f346e0b2eda703587c4cd1c310ec1d.tar.xz
mrst-s0i3-test-015640edb1f346e0b2eda703587c4cd1c310ec1d.zip
[SCSI] sg: fix q->queue_lock on scsi_error_handler path
sg_rq_end_io() is called via rq->end_io. In some rare cases, sg_rq_end_io calls blk_put_request/blk_rq_unmap_user (when a program issuing a command has gone before the command completion; e.g. by interrupting a program issuing a command before the command completes). We can't call blk_put_request/blk_rq_unmap_user in interrupt so the commit c96952ed7031e7c576ecf90cf95b8ec099d5295a uses execute_in_process_context(). The problem is that scsi_error_handler() calls rq->end_io too. We can't call blk_put_request/blk_rq_unmap_user too in this path (we hold q->queue_lock). To avoid the above problem, in these rare cases, this patch always uses schedule_work() instead of execute_in_process_context(). Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> Acked-by: Douglas Gilbert <dgilbert@interlog.com> Cc: Stable Tree <stable@kernel.org> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions