Displaying 3 results from an estimated 3 matches for "retry_flush".
2019 Oct 01
0
[nbdkit PATCH 3/6] retry: Check next_ops->can_FOO on retry
...S;
+ return -1;
+ }
+ if (next_ops->can_trim (nxdata) != 1) {
+ *err = EROFS;
+ r = -1;
+ }
+ else
+ r = next_ops->trim (nxdata, count, offset, flags, err);
if (r == -1 && do_retry (h, &data, next_ops, nxdata, err)) goto again;
return r;
@@ -253,7 +275,12 @@ retry_flush (struct nbdkit_next_ops *next_ops, void *nxdata,
int r;
again:
- r = next_ops->flush (nxdata, flags, err);
+ if (next_ops->can_flush (nxdata) != 1) {
+ *err = EIO;
+ r = -1;
+ }
+ else
+ r = next_ops->flush (nxdata, flags, err);
if (r == -1 && do_retry (h, &am...
2019 Oct 01
9
[nbdkit PATCH v2 0/6] Improve retry filter
Includes a rework of the previously posted patch for --run
improvements (mostly with improved comments and commit message; I
decided that waiting for the captive nbdkit to exit was overkill), and
four new patches. The tests are intentionally separate, to allow
rearranging the order of the series to see the failures being fixed.
Eric Blake (6):
server: Propagate unexpected nbdkit failure with
2019 Oct 07
6
[nbdkit PATCH 0/5] More retry fixes
I think this is my last round of patches for issues I identified with
the retry filter. With this in place, it should be safe to interject
another filter in between retry and the plugin.
Eric Blake (5):
retry: Don't call into closed plugin
tests: Refactor test-retry-reopen-fail.sh
tests: Enhance retry test to cover failed reopen
server: Move prepare/finalize/close recursion to