search for: send_info

...\n", 333: (unsigned long long)dg->payload_size); 334: return VMCI_ERROR_INVALID_ARGS; 335: } This provides an upper bound of 69,632 bytes, but it doesn?t relate the payload size to the actual size of the user-supplied datagram. I think there should be a comparison with 'send_info.len? in vmci_host_do_send_datagram(). Please let me know if you have any questions or need more details. Thanks, -David

...\n", 333: (unsigned long long)dg->payload_size); 334: return VMCI_ERROR_INVALID_ARGS; 335: } This provides an upper bound of 69,632 bytes, but it doesn?t relate the payload size to the actual size of the user-supplied datagram. I think there should be a comparison with 'send_info.len? in vmci_host_do_send_datagram(). Please let me know if you have any questions or need more details. Thanks, -David

Necessary when writing a client that wants to avoid unnecessary EINVAL errors from sending unaligned requests. At some point, we may want to add synchronous convenience API wrappers that do request splitting or read-modify-write to obey server constraints while still appearing to the library client as accepting any possible request. But such a wrapper should only be synchronous and not copied to

...to email_admin? Thanks ============================== # Worker Code class PostalWorker < BackgrounDRb::MetaWorker set_worker_name :postal_worker def create # this method is called, when worker is loaded for the first time end def email_admin(p_subject,p_body) Emailer.deliver_send_info(p_subject,p_body,Time.now) end end ============================== # Rails controller code class FooController < ApplicationController def bar worker = MiddleMan.worker(:postal_worker) result = worker.email_admin(''Some subject'',''And some body'')...

...host.c b/drivers/misc/vmw_vmci/vmci_host.c index 66fc992..a721b5d 100644 --- a/drivers/misc/vmw_vmci/vmci_host.c +++ b/drivers/misc/vmw_vmci/vmci_host.c @@ -395,6 +395,12 @@ static int vmci_host_do_send_datagram(struct vmci_host_dev *vmci_host_dev, return -EFAULT; } + if (VMCI_DG_SIZE(dg) != send_info.len) { + vmci_ioctl_err("datagram size mismatch\n"); + kfree(dg); + return -EINVAL; + } + pr_devel("Datagram dst (handle=0x%x:0x%x) src (handle=0x%x:0x%x), payload (size=%llu bytes)\n", dg->dst.context, dg->dst.resource, dg->src.context, dg->src.resource...

...host.c b/drivers/misc/vmw_vmci/vmci_host.c index 66fc992..a721b5d 100644 --- a/drivers/misc/vmw_vmci/vmci_host.c +++ b/drivers/misc/vmw_vmci/vmci_host.c @@ -395,6 +395,12 @@ static int vmci_host_do_send_datagram(struct vmci_host_dev *vmci_host_dev, return -EFAULT; } + if (VMCI_DG_SIZE(dg) != send_info.len) { + vmci_ioctl_err("datagram size mismatch\n"); + kfree(dg); + return -EINVAL; + } + pr_devel("Datagram dst (handle=0x%x:0x%x) src (handle=0x%x:0x%x), payload (size=%llu bytes)\n", dg->dst.context, dg->dst.resource, dg->src.context, dg->src.resource...

...nodeid 1812048064 needs fs notify#012 Aug 18 13:12:31 nodo1 cluster-dlm: check_fencing_done: check_fencing done#012 Aug 18 13:12:31 nodo1 cluster-dlm: check_quorum_done: check_quorum disabled#012 Aug 18 13:12:31 nodo1 cluster-dlm: check_fs_done: check_fs done#012 Aug 18 13:12:31 nodo1 cluster-dlm: send_info: send_start cg 3 flags 2 counts 2 1 0 1 1#012 Aug 18 13:12:31 nodo1 cluster-dlm: set_fs_notified: set_fs_notified no nodeid 1812048064#012 Aug 18 13:12:31 nodo1 cluster-dlm: set_fs_notified: set_fs_notified no nodeid 1812048064#012 Aug 18 13:12:31 nodo1 cluster-dlm: set_fs_notified: set_fs_notified...

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with

Well, I'm not quite done (I still want to get nbdinfo to work on a single nbd connection for all cases when reading the heads of the file is not required), but I'm happy with patches 1-11, and 12-13 show where I'm headed for getting NBD_OPT_INFO to work. Posting now to see if some of the earlier patches are ready to commit while I continue working on the latter half. Eric Blake (13):