Re: [PATCH] chardev: fix segfault in finalize

2022-09-20 Thread Maksim Davydov
Hi!Could you send a pull request? 26.08.2022, 11:21, "Marc-André Lureau" :Hi  On Thu, Aug 25, 2022 at 9:02 PM Maksim Davydov wrote:If finalize chardev-msmouse or chardev-wctable is called immediately afterinit it cases QEMU to crash with segfault. This happens because

Re: [PATCH] chardev: fix segfault in finalize

2022-09-14 Thread Maksim Davydov
+ vsementsov@- pbonzini@   26.08.2022, 11:21, "Marc-André Lureau" :Hi  On Thu, Aug 25, 2022 at 9:02 PM Maksim Davydov wrote:If finalize chardev-msmouse or chardev-wctable is called immediately afterinit it cases QEMU to crash with segfault. This happens because

Re: [PATCH] chardev: fix segfault in finalize

2022-09-08 Thread Vladimir Sementsov-Ogievskiy
On 8/25/22 19:52, Maksim Davydov wrote: If finalize chardev-msmouse or chardev-wctable is called immediately after init it cases QEMU to crash with segfault. This happens because of QTAILQ_REMOVE in qemu_input_handler_unregister tries to dereference NULL pointer. For instance, this error can be

Re: [PATCH] chardev: fix segfault in finalize

2022-08-26 Thread Marc-André Lureau
Hi On Thu, Aug 25, 2022 at 9:02 PM Maksim Davydov wrote: > If finalize chardev-msmouse or chardev-wctable is called immediately after > init it cases QEMU to crash with segfault. This happens because of > QTAILQ_REMOVE in qemu_input_handler_unregister tries to dereference > NULL pointer. > For

[PATCH] chardev: fix segfault in finalize

2022-08-25 Thread Maksim Davydov
If finalize chardev-msmouse or chardev-wctable is called immediately after init it cases QEMU to crash with segfault. This happens because of QTAILQ_REMOVE in qemu_input_handler_unregister tries to dereference NULL pointer. For instance, this error can be reproduced via `qom-list-properties`