[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-block] [PATCH v3 1/3] blkdebug: fix one shot rule processing
From: |
Marc Olson |
Subject: |
[Qemu-block] [PATCH v3 1/3] blkdebug: fix one shot rule processing |
Date: |
Sun, 11 Nov 2018 23:06:36 -0800 |
If 'once' is specified, the rule should execute just once, regardless if
it is supposed to return an error or not. Take the example where you
want the first IO to an LBA to succeed, but subsequent IOs to fail. You
could either use state transitions, or create two rules, one with
error = 0 and once set to true, and one with a non-zero error.
Signed-off-by: Marc Olson <address@hidden>
---
block/blkdebug.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block/blkdebug.c b/block/blkdebug.c
index 0759452..327049b 100644
--- a/block/blkdebug.c
+++ b/block/blkdebug.c
@@ -488,7 +488,7 @@ static int rule_check(BlockDriverState *bs, uint64_t
offset, uint64_t bytes)
}
}
- if (!rule || !rule->options.inject.error) {
+ if (!rule) {
return 0;
}
@@ -500,7 +500,7 @@ static int rule_check(BlockDriverState *bs, uint64_t
offset, uint64_t bytes)
remove_rule(rule);
}
- if (!immediately) {
+ if (error && !immediately) {
aio_co_schedule(qemu_get_current_aio_context(), qemu_coroutine_self());
qemu_coroutine_yield();
}
--
2.7.4