diff options
author | Dave Chinner <dchinner@redhat.com> | 2010-07-13 17:50:50 +1000 |
---|---|---|
committer | Jens Axboe <jaxboe@fusionio.com> | 2010-08-07 18:26:29 +0200 |
commit | f10d9f617a65905c556c3b37c9b9646ae7d04ed7 (patch) | |
tree | 0e1d1a28578e8c1b2115b8486add3b235f7e3619 /block/blk-lib.c | |
parent | 2669b19fa4debcdd6a660ace1a124c0900f113e6 (diff) | |
download | linux-3.10-f10d9f617a65905c556c3b37c9b9646ae7d04ed7.tar.gz linux-3.10-f10d9f617a65905c556c3b37c9b9646ae7d04ed7.tar.bz2 linux-3.10-f10d9f617a65905c556c3b37c9b9646ae7d04ed7.zip |
blkdev: check for valid request queue before issuing flush
Issuing a blkdev_issue_flush() on an unconfigured loop device causes a panic as
q->make_request_fn is not configured. This can occur when trying to mount the
unconfigured loop device as an XFS filesystem. There are no guards that catch
the bio before the request function is called because we don't add a payload to
the bio. Instead, manually check this case as soon as we have a pointer to the
queue to flush.
Signed-off-by: Dave Chinner <dchinner@redhat.com>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'block/blk-lib.c')
0 files changed, 0 insertions, 0 deletions