search for: socket_fd

...else if (strcmp (key, "uri") == 0) uri = value; else if (strcmp (key, "command") == 0 || strcmp (key, "arg") == 0) { @@ -220,23 +235,25 @@ static int nbdplug_config_complete (void) { int c = !!sockname + !!hostname + !!uri + - (command.size > 0) + (socket_fd >= 0); + (command.size > 0) + (socket_fd >= 0) + !!raw_cid; /* Check the user passed exactly one connection parameter. */ if (c > 1) { nbdkit_error ("cannot mix Unix ‘socket’, TCP ‘hostname’/‘port’, " - "‘command’, ‘socket-fd’ and ‘uri’ par...

...uot;) == 0) > uri = value; > else if (strcmp (key, "command") == 0 || strcmp (key, "arg") == 0) { > @@ -220,23 +235,25 @@ static int > nbdplug_config_complete (void) > { > int c = !!sockname + !!hostname + !!uri + > - (command.size > 0) + (socket_fd >= 0); > + (command.size > 0) + (socket_fd >= 0) + !!raw_cid; > > /* Check the user passed exactly one connection parameter. */ > if (c > 1) { > nbdkit_error ("cannot mix Unix ‘socket’, TCP ‘hostname’/‘port’, " > - "‘comma...

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

Hi, This is an initial implementation of a vhost-user backend for the VirtIO RPMB device. The device is currently in the draft of the next VirtIO specification and describes block device which uses combination of a key, nonce, hashing and a persistent write counter to prevent replay attacks (hence Replay Protected Memory Block). It is implemented as a vhost-user device because we want to

...oint pending on future shared library load? (y or [n]) n (gdb) break create_mail_process Breakpoint 1 at 0x804fc64: file mail-process.c, line 542. (gdb) cont Continuing. Detaching after fork from child process 31212. Breakpoint 1, create_mail_process (process_type=PROCESS_TYPE_IMAP, set=0x8070330, socket_fd=21, local_ip=0x8077468, remote_ip=0x807747c, user=0x806c322 "test at redmountainorganics.com", args=0x806c370, dump_capability=false) at mail-process.c:542 542 { (gdb) p *args $1 = 0x0 (gdb) bt #0 create_mail_process (process_type=PROCESS_TYPE_IMAP, set=0x8070330, socket_fd=21...

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

On Thu, Aug 06, 2020 at 09:23:46PM -0500, Eric Blake wrote: > + if (!filename == !directory) { A bit tricksy. In plugins/nbd/nbd.c I used: int c = !!sockname + !!hostname + !!uri + (command.size > 0) + (socket_fd >= 0) + !!raw_cid; /* Check the user passed exactly one connection parameter. */ if (c > 1) { nbdkit_error ("cannot mix Unix ‘socket’, TCP ‘hostname’/‘port’, ‘vsock’, " "‘command’, ‘socket-fd’ and ‘uri’ parameters"); return -1; } if (c ==...

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

Here's changes to the file plugin (which I'm happy with) and a new exportname filter (which is still at RFC stage; I need to finish implementing strict mode in .open, and add tests). I also discovered that we really want .list_exports and .open to know when they are used on plaintext vs. tls clients for --tls=on, and we may want to split out a new .default_export callback rather than