Displaying 9 results from an estimated 9 matches for "requested_exportnam".
Did you mean:
requested_exportname
2018 Aug 06
3
[PATCH nbdkit v2] protocol: Implement NBD_OPT_GO.
There's no substantial difference over v1, I simply fixed a few
whitespace issues, moved one struct around and tidied up the comments.
Rich.
2018 Nov 29
2
[nbdkit PATCH] connections: Implement NBD_OPT_INFO
..."number of information requests incorrect", optname);
if (send_newstyle_option_reply (conn, option, NBD_REP_ERR_INVALID)
== -1)
return -1;
@@ -827,9 +830,9 @@ _negotiate_handshake_newstyle_options (struct connection *conn)
}
memcpy (requested_exportname, &data[4], exportnamelen);
requested_exportname[exportnamelen] = '\0';
- debug ("newstyle negotiation: NBD_OPT_GO: "
+ debug ("newstyle negotiation: %s: "
"client requested export '%s' (ignored)",
-...
2018 Aug 06
0
[PATCH nbdkit v2] protocol: Implement NBD_OPT_GO.
...6");
+
+ if (send_newstyle_option_reply (conn, option, NBD_REP_ERR_INVALID)
+ == -1)
+ return -1;
+ continue;
+ }
+
+ {
+ uint32_t exportnamelen;
+ uint16_t nrinfos;
+ uint16_t info;
+ size_t i;
+ CLEANUP_FREE char *requested_exportname = NULL;
+
+ /* Validate the name length and number of INFO requests. */
+ memcpy (&exportnamelen, &data[0], 4);
+ exportnamelen = be32toh (exportnamelen);
+ if (exportnamelen > optlen-6 /* NB optlen >= 6, see above */) {
+ debug ("newstyle ne...
2019 Sep 10
0
[PATCH nbdkit] server: Add nbdkit_export_name() to allow export name to be read.
...tyle_options (struct connection *conn)
continue;
}
- /* As with NBD_OPT_EXPORT_NAME we print the export name and then
- * ignore it.
+ /* As with NBD_OPT_EXPORT_NAME we print the export name and
+ * save it in the connection.
*/
- requested_exportname = malloc (exportnamelen+1);
- if (requested_exportname == NULL) {
+ free (conn->exportname);
+ conn->exportname = malloc (exportnamelen+1);
+ if (conn->exportname == NULL) {
nbdkit_error ("malloc: %m");
return -1;
}
-...
2018 Aug 04
3
[PATCH nbdkit] protocol: Implement NBD_OPT_GO.
This is only lightly tested (against just qemu NBD client), and the
code might be structured a little better as the
_negotiate_handshake_newstyle_options function has now grown to be
huge. Anyway works for me.
Rich.
2019 Sep 10
2
[PATCH nbdkit] server: Add nbdkit_export_name() to allow export name to be read.
This is the sort of thing I had in mind for option (1) here:
https://www.redhat.com/archives/libguestfs/2019-September/msg00047.html
It does reveal that the way we currently list exports is naive to say
the least ...
Rich.
2019 Sep 12
4
[PATCH nbdkit v2 0/3] Access export name from plugins.
The previous incomplete patch was here:
https://www.redhat.com/archives/libguestfs/2019-September/msg00049.html
based on earlier discussion here:
https://www.redhat.com/archives/libguestfs/2019-September/msg00047.html
In v2:
- The previous patch was incomplete. This version completes it by
adding tests and extending nbdkit-sh-plugin.
- nbdkit_export_name now returns NULL for error,
2019 Mar 18
0
[PATCH nbdkit 2/2] server: Split out NBD protocol code from connections code.
...optname);
-
- if (send_newstyle_option_reply (conn, option, NBD_REP_ERR_INVALID)
- == -1)
- return -1;
- continue;
- }
-
- {
- uint32_t exportnamelen;
- uint16_t nrinfos;
- uint16_t info;
- size_t i;
- CLEANUP_FREE char *requested_exportname = NULL;
-
- /* Validate the name length and number of INFO requests. */
- memcpy (&exportnamelen, &data[0], 4);
- exportnamelen = be32toh (exportnamelen);
- if (exportnamelen > optlen-6 /* NB optlen >= 6, see above */) {
- debug ("newstyle ne...
2019 Mar 18
3
[PATCH nbdkit 0/2] server: Split out NBD protocol code from connections code.
These are a couple of patches in preparation for the Block Status
implementation. While the patches (especially the second one) are
very large they are really just elementary code motion.
Rich.