linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Richard Weinberger <richard@nod.at>, Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org, linux-um@lists.infradead.org,
	dwalter@google.com, anton.ivanov@cambridgegreys.com
Subject: Re: [PATCH, RFC] ubd: remove use of blk_rq_map_sg
Date: Mon, 15 Oct 2018 16:04:20 -0600	[thread overview]
Message-ID: <a33c7dfb-3eb6-3955-0336-257b8fcbfbe7@kernel.dk> (raw)
In-Reply-To: <48119384.A7YGth2QHM@blindfold>

On 10/15/18 3:46 PM, Richard Weinberger wrote:
> Am Montag, 15. Oktober 2018, 22:55:29 CEST schrieb Christoph Hellwig:
>> On Mon, Oct 15, 2018 at 10:42:47PM +0200, Richard Weinberger wrote:
>>>> Sadly not. I'm checking now what exactly is broken.
>>>
>>> I take this back. Christoph's fixup makes reading work.
>>> The previous version corrupted my test block device in interesting ways
>>> and confused all tests.
>>> But the removal of blk_rq_map_sg() still has issues.
>>> Now the device blocks endless upon flush.
>>
>> I suspect we still need to special case flush.  Updated patch below
>> including your other suggestion:
> 
> While playing further with the patch I managed to hit
> BUG_ON(blk_queued_rq(rq)) in blk_mq_requeue_request().
> 
> UML requeues the request in ubd_queue_one_vec() if it was not able
> to submit the request to the host io-thread.
> The fd can return -EAGAIN, then UML has to try later.
> 
> Isn't this allowed in that context?

It is, the problem is that queue_one_vec() doesn't always return an
error. The caller is doing a loop per bio, so we can encounter an
error, requeue, and then the caller will call us again. We're in
an illegal state at that point, and the next requeue will make that
obvious since it's already pending. Actually, both the caller and
ubd_queue_one_vec() also requeue. So it's a bit of a mess, the below
might help.


--- arch/um//drivers/ubd_kern.c~	2018-10-15 16:01:06.813391968 -0600
+++ arch/um/drivers/ubd_kern.c	2018-10-15 16:03:51.870657352 -0600
@@ -1294,7 +1294,7 @@
 {
 	struct ubd *dev = hctx->queue->queuedata;
 	struct io_thread_req *io_req;
-	int written;
+	int ret;
 
 	io_req = kmalloc(sizeof(struct io_thread_req), GFP_ATOMIC);
 	if (!io_req)
@@ -1328,15 +1328,14 @@
 		}
 	}
 
-	written = os_write_file(thread_fd, &io_req, sizeof(io_req));
-	if (written != sizeof(io_req)) {
+	ret = os_write_file(thread_fd, &io_req, sizeof(io_req));
+	if (ret != sizeof(io_req)) {
 		if (written != -EAGAIN)
-			pr_err("write to io thread failed: %d\n", -written);
-		blk_mq_requeue_request(io_req->req, true);
+			pr_err("write to io thread failed: %d\n", -ret);
 		kfree(io_req);
 	}
 
-	return 0;
+	return ret;
 }
 
 static blk_status_t ubd_queue_rq(struct blk_mq_hw_ctx *hctx,

-- 
Jens Axboe


_______________________________________________
linux-um mailing list
linux-um@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-um


  reply	other threads:[~2018-10-15 22:04 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
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 [this message]
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=a33c7dfb-3eb6-3955-0336-257b8fcbfbe7@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=anton.ivanov@cambridgegreys.com \
    --cc=dwalter@google.com \
    --cc=hch@lst.de \
    --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).