block: Don't access request after it might be freed
authorRoland Dreier <roland@purestorage.com>
Thu, 22 Nov 2012 10:00:11 +0000 (02:00 -0800)
committerBen Hutchings <ben@decadent.org.uk>
Thu, 6 Dec 2012 11:20:35 +0000 (11:20 +0000)
commit32eb44e290d1151e9eb26f57564dae6966190685
treeadd2e86801ceab4d9fd8fd543e240c0ec7e98a71
parentde268a9f92b3b2504e9f87db3b4dd609aafb255f
block: Don't access request after it might be freed

commit 893d290f1d7496db97c9471bc352ad4a11dc8a25 upstream.

After we've done __elv_add_request() and __blk_run_queue() in
blk_execute_rq_nowait(), the request might finish and be freed
immediately.  Therefore checking if the type is REQ_TYPE_PM_RESUME
isn't safe afterwards, because if it isn't, rq might be gone.
Instead, check beforehand and stash the result in a temporary.

This fixes crashes in blk_execute_rq_nowait() I get occasionally when
running with lots of memory debugging options enabled -- I think this
race is usually harmless because the window for rq to be reallocated
is so small.

Signed-off-by: Roland Dreier <roland@purestorage.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
[bwh: Backported to 3.2: adjust context]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
block/blk-exec.c