From: Florian Westphal <fw@strlen.de>
To: "Егор Будюкин" <zhora.budyukin111@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Minor memory leak at iptables/nft.c
Date: Thu, 13 Mar 2025 17:11:20 +0100 [thread overview]
Message-ID: <20250313161120.GC32238@breakpoint.cc> (raw)
In-Reply-To: <CAAv0m29bukaAnKkM=ht2vPA=0_8Fii24aSTj4MMcXTW5kNJJkA@mail.gmail.com>
Егор Будюкин <zhora.budyukin111@gmail.com> wrote:
> I'd like to propose a patch fixing a minor memory leak found with a
> static analyzer. It can be found at __add_target and __add_match
> functions, where info is callocated as a buffer and not freed
> afterwards.
I don't see a bug in either of these functions.
struct nftnl_expr assumes ownership of the allocated blob.
prev parent reply other threads:[~2025-03-13 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 14:55 Minor memory leak at iptables/nft.c Егор Будюкин
2025-03-13 16:11 ` Florian Westphal [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=20250313161120.GC32238@breakpoint.cc \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=zhora.budyukin111@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.