Displaying 2 results from an estimated 2 matches for "ef8303e".
Did you mean:
5f83036
2020 Sep 04
0
[libnbd PATCH 1/2] api: Add nbd_set_strict_mode
..., flags);
- return -1;
+ if ((flags & ~LIBNBD_CMD_FLAG_REQ_ONE) != 0) {
+ set_error (EINVAL, "invalid flag: %" PRIu32, flags);
+ return -1;
+ }
}
if (count == 0) { /* NBD protocol forbids this. */
diff --git a/tests/errors.c b/tests/errors.c
index ef8303e..a8e1b0c 100644
--- a/tests/errors.c
+++ b/tests/errors.c
@@ -86,6 +86,7 @@ main (int argc, char *argv[])
*/
const char *cmd[] = { "nbdkit", "-s", "--exit-with-parent", "sh",
script, NULL };
+ uint32_t strict;
progname = a...
2020 Sep 04
4
[RFC libnbd PATCH 0/2] Add knobs for client- vs. server-side validation
We have been inconsistent on how much we reject client-side without
even consulting the server, vs. how much we depend on the server to
detect failure (even if our request can be deemed undefined per NBD
protocol). I'd like to change it so that by default, we reject as
much as we can client-side for less traffic, but where the user can
also change things on the fly for server-side integration