search for: nbd_connect_socket

On Fri, Oct 04, 2019 at 03:08:15PM -0500, Eric Blake wrote: > Do we want a mode where we can hand a socket to libnbd that has > already completed handshake phase and is immediately ready for > transaction phase? I've seen posts describing alternative programs > that do their own handshake before using ioctls to hand an open > socket to the kernel kvm module, which only needs to

On 10/4/19 2:50 PM, Richard W.M. Jones wrote: > This allows us to connect directly to a connected socket. How exactly > the socket is created and connected to the NBD server is left up to > the main program. > > The only real complexity in this patch is allowing file descriptors to > be passed to libnbd APIs. Luckily in C and Python we can treat them > exactly as integers,

...{ + default_call with + args = [ Fd "sock" ]; ret = RErr; + permitted_states = [ Created ]; + shortdesc = "connect directly to a connected socket"; + longdesc = "\ +Begin connecting to the connected socket C<fd>. +Parameters behave as documented in L<nbd_connect_socket(3)>. + You can check if the connection is still connecting by calling L<nbd_aio_is_connecting(3)>, or if it has connected to the server and completed the NBD handshake by calling L<nbd_aio_is_ready(3)>, @@ -2758,6 +2791,8 @@ let first_version = [ "get_handshake_flags"...

On Wed, Mar 18, 2020 at 01:46:14PM -0400, habib dan aouta wrote: > Hello Richard, > > Hope you are doing well. My name is Habib and I am current student > at the University of North Carolina at Charlotte(U.S). I am > currently following your Libnbd client fuzzing tutorial from the > Wordpress articles

...-wrapper @@ when I try that command it gives me an error saying Libnbd-fuzz-wrapper.c is not an EFL binary. Then I tried to compile Libnbd-fuzz-wrapper.c first into an executable file and then I get the following error: libnbd-fuzz-wrapper.c:130:3: warning: implicit declaration of function 'nbd_connect_socket' [-Wimplicit-function-declaration] nbd_connect_socket (nbd, sock); I also added the #include<libnbd.h> into the Libnbd-fuzz-wrapper.c but still getting the same error. Finally I ran this command : ld -lnbd —verbose and I found out libnbd library is missing attempt to open //usr/loca...

...-wrapper @@ when I try that command it gives me an error saying Libnbd-fuzz-wrapper.c is not an EFL binary. Then I tried to compile Libnbd-fuzz-wrapper.c first into an executable file and then I get the following error: libnbd-fuzz-wrapper.c:130:3: warning: implicit declaration of function 'nbd_connect_socket' [-Wimplicit-function-declaration] nbd_connect_socket (nbd, sock); I also added the #include<libnbd.h> into the Libnbd-fuzz-wrapper.c but still getting the same error. Finally I ran this command : ld -lnbd —verbose and I found out libnbd library is missing attempt to open //usr/loca...

For commands with long names and/or short descriptors, you can end up going over 72 characters in the first line of the man page (causing podwrapper to complain). Wrap these lines. --- generator/generator | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/generator/generator b/generator/generator index 7d3f656..ad1cb6b 100755 --- a/generator/generator +++ b/generator/generator

The first four patches are fairly routine clean up and can be reviewed/applied on their own. The fifth patch is problematic as described below. At the moment if you want to proxy through to qemu-nbd (eg. for handling qcow2 files) it's rather complicated and you end up having to manage the sockets and clean up yourself. However the library we use for the proxying supports a perfectly good

...tember/msg00128.html remote code execution vulnerability See the full announcement here: https://www.redhat.com/archives/libguestfs/2019-October/msg00060.html New APIs nbd_can_fast_zero(3) Test support by the server for fast zeroing (Eric Blake). nbd_connect_socket(3) nbd_aio_connect_socket(3) Connect to a local connected socket which you create in your main program using your own chosen method. nbd_connect_systemd_socket_activation(3) nbd_aio_connect_systemd_socket_activation(3) Connect to local processe...

...()); + exit (EXIT_FAILURE); + } + break; + + case MODE_FD: + if (sscanf (argv[optind], "%d", &fd) != 1) { + fprintf (stderr, "%s: could not parse file descriptor: %s\n\n", + argv[0], argv[optind]); + exit (EXIT_FAILURE); + } + if (nbd_connect_socket (nbd, fd) == -1) { + fprintf (stderr, "%s\n", nbd_get_error ()); + exit (EXIT_FAILURE); + } + break; + + case MODE_TCP: + if (nbd_connect_tcp (nbd, argv[optind], argv[optind+1]) == -1) { + fprintf (stderr, "%s\n", nbd_get_error ()); + exit (EXIT_FAI...

...de. Connect to an NBD server on a Unix domain socket. See also L<nbd_connect_unix(3)>. +=item B<--vsock> CID PORT + +Select vsock mode. Connect to an NBD server on a C<AF_VSOCK> socket. +See also L<nbd_connect_vsock(3)>. + =back =head1 NOTES @@ -294,6 +301,7 @@ L<nbd_connect_socket(3)>, L<nbd_connect_systemd_socket_activation(3)>, L<nbd_connect_tcp(3)>, L<nbd_connect_unix(3)>, +L<nbd_connect_vsock(3)>, L<libguestfs(3)>, L<guestfish(1)>, L<guestmount(1)>, diff --git a/generator/generator b/generator/generator index 54a8eb7..89...

Another series on top of my exportname filter, marking off another todo bullet point. With this, you can now use the NBD plugin as a transparent passthrough of all export names served by the remote server in both directions (list advertisement server to client, and export name from client to server). Eric Blake (3): nbd: Implement .default_export, .export_description nbd: Add

I fixed the deadlock - turned out to be an actual bug in the nbd plugin (see patch 8). I changed the command syntax so it's now: nbdkit nbd command=qemu arg=-f arg=qcow2 arg=/path/to/disk.qcow2 Nir wrote: 18:08 < nsoffer> rwmjones: regarding the nbd proxy patches, did you have specific flow that help us? 18:08 < nsoffer> rwmjones: or this is just a way to support qcow2 in the

This is a series of patches to libnbd and nbdkit adding AF_VSOCK support. On the host side it allows you to start an nbdkit instance which listens on a virtio-vsock socket: $ ./nbdkit -fv --vsock memory 1G ... nbdkit: debug: bound to vsock 2:10809 On the guest side you can then use libnbd to connect to the server: $ ./run nbdsh -c 'h.connect_vsock(2, 10809)' -c

...case MODE_FD: > + if (sscanf (argv[optind], "%d", &fd) != 1) { Overflow is undetected. > + fprintf (stderr, "%s: could not parse file descriptor: %s\n\n", > + argv[0], argv[optind]); > + exit (EXIT_FAILURE); > + } > + if (nbd_connect_socket (nbd, fd) == -1) { > + fprintf (stderr, "%s\n", nbd_get_error ()); > + exit (EXIT_FAILURE); > + } > + break; > + > + > + /* Create the FUSE args. */ > + if (fuse_opt_add_arg (&fuse_args, argv[0]) == -1) { > + fuse_opt_error: > + per...

It's been several weeks since I posted v2 (I got distracted by improving libnbd to better test things, which in turn surfaced some major memory leak problems in nbdsh that are now fixed). Many of the patches are minor rebases from v2, with the biggest changes being fallout from: - patch 2: rename nbdkit_add_default_export to nbdkit_use_default_export - overall: this missed 1.22, so update