[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1251992870.3084.125.camel@blaa>
Date: Thu, 03 Sep 2009 16:47:50 +0100
From: Mark McLoughlin <markmc@...hat.com>
To: Jens Axboe <jens.axboe@...cle.com>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
virtualization <virtualization@...ts.linux-foundation.org>,
dm-devel <dm-devel@...hat.com>,
Rusty Russell <rusty@...tcorp.com.au>,
Mikulas Patocka <mpatocka@...hat.com>,
Alasdair Kergon <agk@...hat.com>, Neil Brown <neilb@...e.de>,
Christoph Hellwig <hch@...radead.org>
Subject: [PATCH resend] block: silently error unsupported empty barriers too
With 2.6.31-rc5 in a KVM guest using dm and virtio_blk, we see the
following errors:
end_request: I/O error, dev vda, sector 0
end_request: I/O error, dev vda, sector 0
The errors go away if dm stops submitting empty barriers, by reverting:
commit 52b1fd5a27c625c78373e024bf570af3c9d44a79
Author: Mikulas Patocka <mpatocka@...hat.com>
dm: send empty barriers to targets in dm_flush
We should error all barriers, even empty barriers, on devices like
virtio_blk which don't support them.
See also:
https://bugzilla.redhat.com/514901
Signed-off-by: Mark McLoughlin <markmc@...hat.com>
Cc: Rusty Russell <rusty@...tcorp.com.au>
Cc: Mikulas Patocka <mpatocka@...hat.com>
Cc: Alasdair G Kergon <agk@...hat.com>
Cc: Neil Brown <neilb@...e.de>
Cc: Christoph Hellwig <hch@...radead.org>
---
block/blk-core.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/block/blk-core.c b/block/blk-core.c
index e3299a7..35ad2bb 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -1163,8 +1163,7 @@ static int __make_request(struct request_queue *q, struct bio *bio)
const int unplug = bio_unplug(bio);
int rw_flags;
- if (bio_barrier(bio) && bio_has_data(bio) &&
- (q->next_ordered == QUEUE_ORDERED_NONE)) {
+ if (bio_barrier(bio) && (q->next_ordered == QUEUE_ORDERED_NONE)) {
bio_endio(bio, -EOPNOTSUPP);
return 0;
}
--
1.6.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists