The patch titled
device mapper not reporting no-barrier-support?
has been removed from the -mm tree. Its filename was
device-mapper-not-reporting-no-barrier-support.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: device mapper not reporting no-barrier-support?
From: Jens Axboe <jens.axboe@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
block/blk-barrier.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff -puN block/blk-barrier.c~device-mapper-not-reporting-no-barrier-support block/blk-barrier.c
--- a/block/blk-barrier.c~device-mapper-not-reporting-no-barrier-support
+++ a/block/blk-barrier.c
@@ -259,8 +259,11 @@ int blk_do_ordered(struct request_queue
static void bio_end_empty_barrier(struct bio *bio, int err)
{
- if (err)
+ if (err) {
+ if (err == -EOPNOTSUPP)
+ set_bit(BIO_EOPNOTSUPP, &bio->bi_flags);
clear_bit(BIO_UPTODATE, &bio->bi_flags);
+ }
complete(bio->bi_private);
}
@@ -309,7 +312,9 @@ int blkdev_issue_flush(struct block_devi
*error_sector = bio->bi_sector;
ret = 0;
- if (!bio_flagged(bio, BIO_UPTODATE))
+ if (bio_flagged(bio, BIO_EOPNOTSUPP))
+ ret = -EOPNOTSUPP;
+ else if (!bio_flagged(bio, BIO_UPTODATE))
ret = -EIO;
bio_put(bio);
_
Patches currently in -mm which might be from jens.axboe@xxxxxxxxxx are
origin.patch
drivers-block-viodasdc-use-field_sizeof.patch
git-block.patch
git-block-git-rejects.patch
remove-ps2esdi.patch
kconfig-cleanup-block-kconfig-help-descriptions.patch
kconfig-cleanup-block-kconfigiosched-help-descriptions.patch
block-genhdc-check-class_register-return-value.patch
xen-make-blkif_getgeo-static.patch
block-remove-remaining-__function__-occurances.patch
reiser4.patch
jens-broke-reiser4patch-added-to-mm-tree.patch
reiser4-specify-splice-file-operations.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
