search for: callback_data

The safe_malloc (etc) functions call g->abort_fn on failure. That's not appropriate for language bindings, and we never intended that these internal functions be used from language bindings, that was just a historical accident. This patch series removes any external use of the safe_* functions. Rich.

...event_release_cb, s); + + return s; +} + +/** + * vmci_event_subscribe() - Subscribe to a given event. + * @event: The event to subscribe to. + * @flags: Event flags. VMCI_FLAG_EVENT_* + * @callback: The callback to invoke upon the event. + * @callback_data: Data to pass to the callback. + * @subscription_id: ID used to track subscription. Used with + * vmci_event_unscribe() + * + * Subscribes to the provided event. The callback specified can be fired + * in different contexts depending on what flag is specified while + * registeri...

...event_release_cb, s); + + return s; +} + +/** + * vmci_event_subscribe() - Subscribe to a given event. + * @event: The event to subscribe to. + * @flags: Event flags. VMCI_FLAG_EVENT_* + * @callback: The callback to invoke upon the event. + * @callback_data: Data to pass to the callback. + * @subscription_id: ID used to track subscription. Used with + * vmci_event_unscribe() + * + * Subscribes to the provided event. The callback specified can be fired + * in different contexts depending on what flag is specified while + * registeri...

...Int64 _ | Path _ | SockAddrAndLen _ | StringList _ | UInt _ | UInt32 _ -> () ) args; @@ -3054,6 +3072,9 @@ let print_python_binding name { args; ret } = pr " struct py_aio_buffer *%s_buf;\n" n | Callback (n, _) -> pr " struct %s_%s_data callback_data;\n" name n + | Flags n -> + pr " uint32_t %s_u32;\n" n; + pr " unsigned int %s = 0; /* really uint32_t */\n" n | Int n -> pr " int %s;\n" n | Int64 n -> pr " int64_t %s_i64;\n" n; @@ -3091,6 +3112,7 @@ let pr...

This applies on top of patches 1 & 2 here (instead of patch 3): https://www.redhat.com/archives/libguestfs/2019-May/msg00206.html https://www.redhat.com/archives/libguestfs/2019-May/msg00207.html Rich.

Hi, some of the bindings may try to malloc with 0 bytes as size when closing an handle, because there were no event handlers registered. Since this can have different behaviours in POSIX, avoid that situation altogether by just skipping allocating anything when there were no event handlers. Thanks, Pino Toscano (4): ocaml: do not try to malloc 0 elements in get_all_event_callbacks python:

...0x08064a77 in pbutton_button_release_cb (widget=0x818c908, event=0x820a870, button=0x818d280) at pbutton.c:71 #12 0x0806466b in handle_release_cb (wlist=0x81297f8, widget=0x818c908, event=0x820a870) at widget.c:90 #13 0x0806c5f4 in mainwin_release (widget=0x818c908, event=0x820a870, callback_data=0x0) at main.c:1146 #14 0x40236aec in gtk_marshal_BOOL__POINTER () from /usr/lib/libgtk-1.2.so.0 #15 0x4026a436 in gtk_handlers_run () from /usr/lib/libgtk-1.2.so.0 #16 0x4026976d in gtk_signal_real_emit () from /usr/lib/libgtk-1.2.so.0 #17 0x40267525 in gtk_signal_emit () from /usr/lib/libgtk-1.2....

* * * 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

...se_cb (widget=0x818c908, > event=0x820a870, button=0x818d280) at pbutton.c:71 > #12 0x0806466b in handle_release_cb (wlist=0x81297f8, > widget=0x818c908, > event=0x820a870) at widget.c:90 > #13 0x0806c5f4 in mainwin_release (widget=0x818c908, event=0x820a870, > > callback_data=0x0) at main.c:1146 > #14 0x40236aec in gtk_marshal_BOOL__POINTER () from > /usr/lib/libgtk-1.2.so.0 > #15 0x4026a436 in gtk_handlers_run () from /usr/lib/libgtk-1.2.so.0 > #16 0x4026976d in gtk_signal_real_emit () from > /usr/lib/libgtk-1.2.so.0 > #17 0x40267525 in gtk_signal_emi...

I have just released a source distribution which is the candidate for the 1.0.3 release. At this time I would ask anyone who is willing to help test it to do the following: 1. download the tarball and unzip it: http://prdownloads.sourceforge.net/flac/flac-1.0.3_beta-src.tar.gz?download 2. do ./configure && make && make check This will build all code and run all the tests.

Hi, this patch series fixes some issues discovered by Coverity. Most of them are memory leaks, usually on error; there are also invalid memory access issues. Thanks, Pino Toscano (11): java: link libguestfs_jni against libutils java: fix invalid memory access for FBuffer in struct lists daemon: tsk: properly use GUESTFS_MAX_CHUNK_SIZE edit: fix small memory leak on error java: fix

...vivi_vdock_add (GtkContainer *container, GtkWidget *widget) { ViviVDock *vdock = VIVI_VDOCK (container); @@ -119,16 +143,37 @@ vivi_vdock_child_type (GtkContainer *con } static void +vivi_vdock_forall (GtkContainer *container, gboolean include_internals, + GtkCallback callback, gpointer callback_data) +{ + if (include_internals) { + GTK_CONTAINER_CLASS (vivi_vdock_parent_class)->forall (container, include_internals, + callback, callback_data); + } else { + GList *walk; + + for (walk = VIVI_VDOCK (container)->docklets; walk; walk = walk->next) { + callback (walk->dat...

...andle); int vmci_doorbell_notify(struct vmci_handle handle, u32 priv_flags); u32 vmci_get_context_id(void); bool vmci_is_context_owner(u32 context_id, kuid_t uid); +int vmci_register_vsock_callback(vmci_vsock_cb callback); int vmci_event_subscribe(u32 event, vmci_event_cb callback, void *callback_data, diff --git a/net/vmw_vsock/vmci_transport.c b/net/vmw_vsock/vmci_transport.c index 2eb3f16d53e7..04437f822d82 100644 --- a/net/vmw_vsock/vmci_transport.c +++ b/net/vmw_vsock/vmci_transport.c @@ -2053,19 +2053,22 @@ static bool vmci_check_transport(struct vsock_sock *vsk) return vsk->transport...

...buf; - (* Returning 1 from this callback auto-retires the command. *) - 1 - ) - =head1 EXAMPLES This directory contains examples written in OCaml: diff --git a/ocaml/nbd-c.h b/ocaml/nbd-c.h index ffd51d2..a84d64e 100644 --- a/ocaml/nbd-c.h +++ b/ocaml/nbd-c.h @@ -107,4 +107,12 @@ struct callback_data { extern char **nbd_internal_ocaml_string_list (value); extern value nbd_internal_ocaml_alloc_int32_array (uint32_t *, size_t); +/* Free a generational global root and its container. */ +static inline void +free_root (void *ptr /* unused */, void *rootp) +{ + caml_remove_generational_global_ro...

...@@ vivi_vdock_remove (GtkContainer *contain g_object_unref (widget); } -static GType -vivi_vdock_child_type (GtkContainer *container) -{ - return VIVI_TYPE_DOCKLET; -} - -static void -vivi_vdock_forall (GtkContainer *container, gboolean include_internals, - GtkCallback callback, gpointer callback_data) -{ - if (include_internals) { - GTK_CONTAINER_CLASS (vivi_vdock_parent_class)->forall (container, include_internals, - callback, callback_data); - } else { - GList *walk; - - for (walk = VIVI_VDOCK (container)->docklets; walk; walk = walk->next) { - callback (walk->dat...

...4 _ | Path _ + | Flags _ | Int _ | Int64 _ | Path _ | Mutable _ | SockAddrAndLen _ | StringList _ | UInt _ | UInt32 _ -> assert false ) args in @@ -4025,10 +4060,15 @@ let print_ocaml_binding (name, { args; ret }) = pr " const struct callback_data *_%s = %s;\n" n n; pr " fnv = *_%s->cb;\n" n; pr " %sv = *_%s->data;\n" n n + | Mutable (Int n) -> + pr " %sv = caml_alloc_tuple (1);\n" n; + pr " Store_field (%sv, 0, Val_int (*%s));\n&quot...

* * * 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

...lags are just - * lists of int32 values so we only have to add them together. - */ -static inline uint32_t -Flags_val (value v) -{ - CAMLparam1 (v); - uint32_t r = 0; - - for (; v != Val_emptylist; v = Field (v, 1)) - r += Int32_val (Field (v, 0)); - - CAMLreturnT (uint32_t, r); -} - struct callback_data { value *cb; value *data; diff --git a/ocaml/tests/test_405_pread_structured.ml b/ocaml/tests/test_405_pread_structured.ml index d226af0..e6a3b15 100644 --- a/ocaml/tests/test_405_pread_structured.ml +++ b/ocaml/tests/test_405_pread_structured.ml @@ -54,11 +54,13 @@ let () = NBD.pread_stru...