From: Christoph Hellwig <hch@lst.de>
To: Junichi Nomura <j-nomura@ce.jp.nec.com>
Cc: Jens Axboe <axboe@kernel.dk>,
device-mapper development <dm-devel@redhat.com>,
Christoph Hellwig <hch@lst.de>, Mike Snitzer <snitzer@redhat.com>
Subject: Re: [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones
Date: Fri, 29 May 2015 18:55:45 +0200 [thread overview]
Message-ID: <20150529165545.GB2682@lst.de> (raw)
In-Reply-To: <5565935A.4060408@ce.jp.nec.com>
On Wed, May 27, 2015 at 09:50:18AM +0000, Junichi Nomura wrote:
> Can you test this scenario with your patch?
> 1. Set up a multipath device with fail-over mode
> 2. Write something to the multipath device.
> After the clone request is sent to the primary path
> and before the data goes to the disk,
> down the primary path
> (e.g. echo offline > /sys/block/sdXX/device/state)
> 3. (dm-mpath will retry from the secondary path and
> the write will eventually succeed)
> 4. Verify if the written data is really on the disk
Verified as not working correctly. The patch below fixes it,
but it needs more testing and some comments:
diff --git a/block/blk-core.c b/block/blk-core.c
index aa819a5..54feaae 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -117,7 +117,13 @@ EXPORT_SYMBOL(blk_rq_init);
static void req_bio_endio(struct request *rq, struct bio *bio,
unsigned int nbytes, int error)
{
- if (error && !(rq->cmd_flags & REQ_CLONE))
+ if (rq->cmd_flags & REQ_CLONE) {
+ if (!error && test_bit(BIO_UPTODATE, &bio->bi_flags))
+ bio_advance(bio, nbytes);
+ return;
+ }
+
+ if (error)
clear_bit(BIO_UPTODATE, &bio->bi_flags);
else if (!test_bit(BIO_UPTODATE, &bio->bi_flags))
error = -EIO;
@@ -128,8 +134,7 @@ static void req_bio_endio(struct request *rq, struct bio *bio,
bio_advance(bio, nbytes);
/* don't actually finish bio if it's part of flush sequence */
- if (bio->bi_iter.bi_size == 0 &&
- !(rq->cmd_flags & (REQ_FLUSH_SEQ|REQ_CLONE)))
+ if (bio->bi_iter.bi_size == 0 && !(rq->cmd_flags & REQ_FLUSH_SEQ))
bio_endio(bio, error);
}
next prev parent reply other threads:[~2015-05-29 16:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 13:14 [PATCH for-4.2 1/3] block: remove management of bi_remaining when restoring original bi_end_io Mike Snitzer
2015-05-22 13:14 ` [PATCH for-4.2 2/3] block, dm: don't copy bios for request clones Mike Snitzer
2015-05-26 6:20 ` Junichi Nomura
2015-05-27 8:21 ` Christoph Hellwig
2015-05-27 9:50 ` Junichi Nomura
2015-05-28 6:38 ` Junichi Nomura
2015-05-29 16:54 ` Christoph Hellwig
2015-06-01 1:14 ` Junichi Nomura
2015-06-03 7:37 ` Christoph Hellwig
2015-06-03 23:13 ` Junichi Nomura
2015-05-29 16:55 ` Christoph Hellwig [this message]
2015-06-01 1:19 ` Junichi Nomura
2015-06-03 7:39 ` Christoph Hellwig
2015-05-22 13:14 ` [PATCH for-4.2 3/3] block: remove export for blk_queue_bio Mike Snitzer
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=20150529165545.GB2682@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=snitzer@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.