From: Christoph Hellwig <hch@lst.de>
To: Richard Weinberger <richard@nod.at>
Cc: axboe@kernel.dk, linux-block@vger.kernel.org,
linux-um@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
anton.ivanov@cambridgegreys.com
Subject: Re: [PATCH, RFC] ubd: remove use of blk_rq_map_sg
Date: Mon, 15 Oct 2018 10:45:41 +0200 [thread overview]
Message-ID: <20181015084541.GA27159@lst.de> (raw)
In-Reply-To: <4055590.4i3nx3fRmo@blindfold>
On Mon, Oct 15, 2018 at 10:40:06AM +0200, Richard Weinberger wrote:
> hm, this breaks UML.
> Every filesystem fails to mount.
>
> I did some very rough tests, it seems that the driver fails to read
> data correctly as soon the upper layer tries to get more than 4096 bytes
> at once out of the block device.
>
> IOW:
> dd if=/dev/ubda bs=4096 count=1 skip=0 2>/dev/null| md5sum -
> is good.
> As soon I set bs to something greater it returns garbage.
>
> Later this day I might have some cycles left to debug further.
It probably needs this on top:
diff --git a/arch/um/drivers/ubd_kern.c b/arch/um/drivers/ubd_kern.c
index aafe9c467fdc..5adce80a7ee3 100644
--- a/arch/um/drivers/ubd_kern.c
+++ b/arch/um/drivers/ubd_kern.c
@@ -1290,7 +1290,7 @@ static void cowify_req(struct io_thread_req *req, unsigned long *bitmap,
}
static int ubd_queue_one_vec(struct blk_mq_hw_ctx *hctx, struct request *req,
- sector_t pos, struct bio_vec *bvec)
+ u64 off, struct bio_vec *bvec)
{
struct ubd *dev = hctx->queue->queuedata;
struct io_thread_req *io_req;
@@ -1311,7 +1311,7 @@ static int ubd_queue_one_vec(struct blk_mq_hw_ctx *hctx, struct request *req,
} else {
io_req->fds[1] = dev->fd;
io_req->cow_offset = -1;
- io_req->offset = (unsigned long long)pos << 9;
+ io_req->offset = off;
io_req->length = bvec->bv_len;
io_req->error = 0;
io_req->sector_mask = 0;
@@ -1346,17 +1346,17 @@ static blk_status_t ubd_queue_rq(struct blk_mq_hw_ctx *hctx,
struct bio *bio = req->bio;
struct bvec_iter iter;
struct bio_vec bvec;
- sector_t pos = blk_rq_pos(req);
+ u64 off = (u64)blk_rq_pos(req) << 9;
blk_mq_start_request(req);
for_each_bio(bio) {
bio_for_each_segment(bvec, bio, iter) {
- if (ubd_queue_one_vec(hctx, req, pos, &bvec) < 0) {
+ if (ubd_queue_one_vec(hctx, req, off, &bvec) < 0) {
blk_mq_requeue_request(req, true);
return BLK_STS_OK;
}
- pos += bvec.bv_len;
+ off += bvec.bv_len;
}
}
_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um
next prev parent reply other threads:[~2018-10-15 8:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 6:56 [PATCH, RFC] ubd: remove use of blk_rq_map_sg Christoph Hellwig
2018-10-15 8:40 ` Richard Weinberger
2018-10-15 8:45 ` Christoph Hellwig [this message]
2018-10-15 19:17 ` Richard Weinberger
2018-10-15 20:42 ` Richard Weinberger
2018-10-15 20:55 ` Christoph Hellwig
2018-10-15 21:46 ` Richard Weinberger
2018-10-15 22:04 ` Jens Axboe
2018-10-15 22:44 ` Richard Weinberger
2018-10-16 2:19 ` Jens Axboe
2018-10-16 8:38 ` Richard Weinberger
2018-10-16 14:26 ` Jens Axboe
2018-10-17 6:21 ` Christoph Hellwig
2018-10-18 21:04 ` Richard Weinberger
2018-10-15 8:46 ` Anton Ivanov
2018-10-16 22:43 ` Richard Weinberger
2018-10-17 6:14 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181015084541.GA27159@lst.de \
--to=hch@lst.de \
--cc=anton.ivanov@cambridgegreys.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=richard@nod.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).