aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJens Axboe2011-03-30 02:51:33 -0500
committerJens Axboe2011-04-05 16:51:37 -0500
commit8182924bc5850281985d73c312876746acd390b5 (patch)
treeb095bab06ba6fa55b26047534ebe31004f531e18 /block/blk-core.c
parentb2a8b4b81966094703088a7bc76a313af841924d (diff)
downloadkernel-common-8182924bc5850281985d73c312876746acd390b5.tar.gz
kernel-common-8182924bc5850281985d73c312876746acd390b5.tar.xz
kernel-common-8182924bc5850281985d73c312876746acd390b5.zip
block: dump request state on seeing a corrupted request completion
Currently we just dump a non-informative 'request botched' message. Lets actually try and print something sane to help debug issues around this. Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'block/blk-core.c')
-rw-r--r--block/blk-core.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/block/blk-core.c b/block/blk-core.c
index e0a06236393..4fdf8953efb 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -2163,7 +2163,7 @@ bool blk_update_request(struct request *req, int error, unsigned int nr_bytes)
2163 * size, something has gone terribly wrong. 2163 * size, something has gone terribly wrong.
2164 */ 2164 */
2165 if (blk_rq_bytes(req) < blk_rq_cur_bytes(req)) { 2165 if (blk_rq_bytes(req) < blk_rq_cur_bytes(req)) {
2166 printk(KERN_ERR "blk: request botched\n"); 2166 blk_dump_rq_flags(req, "request botched");
2167 req->__data_len = blk_rq_cur_bytes(req); 2167 req->__data_len = blk_rq_cur_bytes(req);
2168 } 2168 }
2169 2169