Richard W.M. Jones
2023-Feb-16 15:23 UTC
[Libguestfs] [PATCH] python: Avoid leaking py_array along error paths
Tested by reverting bbf396fc5562b4f so that the error path is used, and re-running the reproducer supplied by Google. Rich.
Richard W.M. Jones
2023-Feb-16 15:23 UTC
[Libguestfs] [PATCH] python: Avoid leaking py_array along error paths
See-also: https://listman.redhat.com/archives/libguestfs/2023-February/030730.html Fixes: commit 6ef5837e2d8c5d4d83eff51c0201eb2e08f719de Thanks: Laszlo Ersek --- python/handle.c | 1 + 1 file changed, 1 insertion(+) diff --git a/python/handle.c b/python/handle.c index bf639b5789..717eee83ed 100644 --- a/python/handle.c +++ b/python/handle.c @@ -136,6 +136,7 @@ guestfs_int_py_event_callback_wrapper (guestfs_h *g, buf, buf_len, py_array); if (args == NULL) { PyErr_PrintEx (0); + Py_DECREF (py_array); goto out; } -- 2.39.0
Apparently Analagous Threads
- [PATCH] python: Avoid leaking py_array along error paths
- [PATCH v3 0/2] python: Avoid leaking py_array and py_args in event callbacks
- python: Avoid leaking py_array and py_args in event callbacks
- [PATCH 1/2] python: Avoid crash if callback parameters cannot be built
- [PATCH 2/2] python: Use bytes instead of str for event callback buffer