From e6c55cf1f8b15d48d87174846669a1a1464668cb Mon Sep 17 00:00:00 2001 From: Dirk Engling Date: Sun, 25 Oct 2026 02:49:47 +0200 Subject: Don't let the new iovec allocation dangle in case of a malloc failure for its new data --- ot_iovec.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ot_iovec.c b/ot_iovec.c index bab19e3..cd5b9f9 100644 --- a/ot_iovec.c +++ b/ot_iovec.c @@ -20,6 +20,8 @@ void *iovec_increase(size_t *iovec_entries, struct iovec **iovector, size_t new_ if (!new_vec) return NULL; + *iovector = new_vec; + /* Only allocate after we have a place to store the pointer */ new_data = malloc(new_alloc); if (!new_data) @@ -28,7 +30,6 @@ void *iovec_increase(size_t *iovec_entries, struct iovec **iovector, size_t new_ new_vec[new_entries - 1].iov_base = new_data; new_vec[new_entries - 1].iov_len = new_alloc; - *iovector = new_vec; ++*iovec_entries; return new_data; } -- cgit v1.3