From: Jens Axboe <[email protected]>
To: [email protected], Marcel Holtmann <[email protected]>
Subject: Re: [PATCH liburing] examples/io_uring-test: Fix memory leak
Date: Sun, 12 Jan 2025 15:02:18 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Sun, 12 Jan 2025 19:08:30 +0100, Marcel Holtmann wrote:
> The iovecs structure is leaking even for the succesful case and since
> everything else gets cleaned up before exit, just free the iovecs
> allocated memory as well.
>
>
Applied, thanks!
[1/1] examples/io_uring-test: Fix memory leak
commit: 3124a4619e4daf26b06d48ccf0186a947070c415
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-01-12 22:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 18:08 [PATCH liburing] examples/io_uring-test: Fix memory leak Marcel Holtmann
2025-01-12 22:02 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=173671933815.1103166.13622970529782808467.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox