From: Petr Machata <petrm@nvidia.com>
To: heminhong <heminhong@kylinos.cn>
Cc: <stephen@networkplumber.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH] iproute2: prevent memory leak on error return
Date: Wed, 15 Nov 2023 11:37:16 +0100 [thread overview]
Message-ID: <87ttpnwb5o.fsf@nvidia.com> (raw)
In-Reply-To: <20231114081307.36926-1-heminhong@kylinos.cn>
heminhong <heminhong@kylinos.cn> writes:
> When rtnl_statsdump_req_filter() or rtnl_dump_filter() failed to process,
> just return will cause memory leak.
>
> Signed-off-by: heminhong <heminhong@kylinos.cn>
Reviewed-by: Petr Machata <petrm@nvidia.com>
next prev parent reply other threads:[~2023-11-15 10:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 8:13 [PATCH] iproute2: prevent memory leak on error return heminhong
2023-11-15 10:37 ` Petr Machata [this message]
2023-11-29 4:50 ` patchwork-bot+netdevbpf
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=87ttpnwb5o.fsf@nvidia.com \
--to=petrm@nvidia.com \
--cc=heminhong@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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;
as well as URLs for NNTP newsgroup(s).