From: Stephen Hemminger <stephen@networkplumber.org>
To: 何敏红 <heminhong@kylinos.cn>
Cc: Petr Machata <petrm@nvidia.com>, netdev <netdev@vger.kernel.org>
Subject: Re: 回复: Re: [PATCH] iproute2: prevent memory leak on error return
Date: Tue, 28 Nov 2023 18:47:33 -0800 [thread overview]
Message-ID: <20231128184733.6fc8247e@hermes.local> (raw)
In-Reply-To: <o2sj4kvm3n-o2v307ppr8@nsmail7.0.0--kylin--1>
On Wed, 29 Nov 2023 10:26:37 +0800
何敏红 <heminhong@kylinos.cn> wrote:
> Friendly ping. I think this patch was forgotten.
>
>
>
>
>
>
> ----
>
>
>
>
>
> 主 题：Re: [PATCH] iproute2: prevent memory leak on error return
> 日 期：2023-11-15 18:37
> 发件人：Petr Machata
> 收件人：何敏红;
>
>
> heminhong writes:
>
> > When rtnl_statsdump_req_filter() or rtnl_dump_filter() failed to process,
> > just return will cause memory leak.
> >
> > Signed-off-by: heminhong
>
> Reviewed-by: Petr Machata
>
Please check your repo?
https://github.com/iproute2/iproute2/commit/2c3ebb2ae08a634615e56303d784ddb366e47f04
parent reply other threads:[~2023-11-29 2:47 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <o2sj4kvm3n-o2v307ppr8@nsmail7.0.0--kylin--1>]
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=20231128184733.6fc8247e@hermes.local \
--to=stephen@networkplumber.org \
--cc=heminhong@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox