FUJITA Tomonori wrote:
This patch is against 2.6.28.x, fixes a regression from 2.6.27. This is the modified version of the following patch that is planed to merged into 2.6.30-rc1 in scsi-misc tree: http://git.kernel.org/?p=linux/kernel/git/jejb/scsi-misc-2.6.git;a=commit;h=b35fe25ae156830f85a305afaba837b084458e7a scsi-misc tree has other patches to fix sg oops so the above patch can't be cleanly applied to 2.6.28.x. These patches are too large for 2.6.28.x (needs more testings) so sg in 2.6.28.x still has the oops bugs for now even with this patch. I expect that these patches will go into stable trees too after 2.6.30-rc1 (that is, after more people test them). = From: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx> Subject: [PATCH -stable 2.6.28.x] sg: avoid blk_put_request/blk_rq_unmap_user in interrupt This fixes the following oops: http://bugzilla.kernel.org/show_bug.cgi?id=12612 You can reproduce this bug by interrupting a program before a sg response completes. This leads to the special sg state (the orphan state), then sg calls blk_put_request in interrupt (rq->end_io). The above bug report shows the recursive lock problem because sg calls blk_put_request in interrupt. We could call __blk_put_request here instead however we also need to handle blk_rq_unmap_user here, which can't be called in interrupt too. Signed-off-by: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
Signed-off-by: Douglas Gilbert <dgilbert@xxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
