Displaying 6 results from an estimated 6 matches for "nbd_unlocked_can_fua".
2020 Sep 04
0
[libnbd PATCH 1/2] api: Add nbd_set_strict_mode
...set_error (EINVAL, "invalid flag: %" PRIu32, flags);
- return -1;
- }
+ if ((flags & ~LIBNBD_CMD_FLAG_FUA) != 0) {
+ set_error (EINVAL, "invalid flag: %" PRIu32, flags);
+ return -1;
+ }
- if ((flags & LIBNBD_CMD_FLAG_FUA) != 0 &&
- nbd_unlocked_can_fua (h) != 1) {
- set_error (EINVAL, "server does not support the FUA flag");
- return -1;
+ if ((flags & LIBNBD_CMD_FLAG_FUA) != 0 &&
+ nbd_unlocked_can_fua (h) != 1) {
+ set_error (EINVAL, "server does not support the FUA flag");
+ return -1;...
2020 Sep 11
0
[libnbd PATCH v2 3/5] api: Add nbd_set_strict_mode
...s");
- return -1;
- }
+ if (h->strict & LIBNBD_STRICT_COMMANDS) {
+ if (nbd_unlocked_is_read_only (h) == 1) {
+ set_error (EPERM, "server does not support write operations");
+ return -1;
+ }
- if ((flags & LIBNBD_CMD_FLAG_FUA) != 0 &&
- nbd_unlocked_can_fua (h) != 1) {
- set_error (EINVAL, "server does not support the FUA flag");
- return -1;
+ if ((flags & LIBNBD_CMD_FLAG_FUA) != 0 &&
+ nbd_unlocked_can_fua (h) != 1) {
+ set_error (EINVAL, "server does not support the FUA flag");
+ return -1;...
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
2020 Sep 11
0
[libnbd PATCH v2 2/5] generator: Refactor filtering of accepted OFlags
...320,6 @@ nbd_unlocked_aio_pwrite (struct nbd_handle *h, const void *buf,
return -1;
}
- if ((flags & ~LIBNBD_CMD_FLAG_FUA) != 0) {
- set_error (EINVAL, "invalid flag: %" PRIu32, flags);
- return -1;
- }
-
if ((flags & LIBNBD_CMD_FLAG_FUA) != 0 &&
nbd_unlocked_can_fua (h) != 1) {
set_error (EINVAL, "server does not support the FUA flag");
@@ -362,11 +343,6 @@ nbd_unlocked_aio_flush (struct nbd_handle *h,
return -1;
}
- if (flags != 0) {
- set_error (EINVAL, "invalid flag: %" PRIu32, flags);
- return -1;
- }
-
SET_CALL...
2020 Sep 11
10
[libnbd PATCH v2 0/5] Add knobs for client- vs. server-side validation
In v2:
- now based on my proposal to add LIBNBD_SHUTDOWN_IMMEDIATE
- four flags instead of two: STRICT_FLAGS is new (patch 4),
and STRICT_BOUNDS is separate from STRICT_ZERO_SIZE (patch 5)
- various refactorings for more shared code and less duplication
Eric Blake (5):
api: Add xxx_MASK constant for each Flags type
generator: Refactor filtering of accepted OFlags
api: Add
2019 May 23
2
[PATCH libnbd] api: Get rid of nbd_connection.
This isn't quite finished because not all of the tests or examples
have been updated, but it demonstrates an idea: Should we forget about
the concept of having multiple connections managed under a single
handle?
In this patch there is a single ‘struct nbd_handle *’ which manages a
single state machine and connection (and therefore no nbd_connection).
To connect to a multi-conn server you must