diff options
| author | Jens Axboe <jaxboe@fusionio.com> | 2011-03-30 09:51:33 +0200 |
|---|---|---|
| committer | Jens Axboe <jaxboe@fusionio.com> | 2011-04-05 23:51:37 +0200 |
| commit | 8182924bc5850281985d73c312876746acd390b5 (patch) | |
| tree | b095bab06ba6fa55b26047534ebe31004f531e18 | |
| parent | b2a8b4b81966094703088a7bc76a313af841924d (diff) | |
| download | op-kernel-dev-8182924bc5850281985d73c312876746acd390b5.zip op-kernel-dev-8182924bc5850281985d73c312876746acd390b5.tar.gz | |
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>
| -rw-r--r-- | block/blk-core.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/block/blk-core.c b/block/blk-core.c index e0a0623..4fdf895 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) * size, something has gone terribly wrong. */ if (blk_rq_bytes(req) < blk_rq_cur_bytes(req)) { - printk(KERN_ERR "blk: request botched\n"); + blk_dump_rq_flags(req, "request botched"); req->__data_len = blk_rq_cur_bytes(req); } |
