From: David Marchand <david.marchand@redhat.com>
To: Jun Qiu <jun.qiu@jaguarmicro.com>
Cc: dev@dpdk.org, yipeng1.wang@intel.com, lei.cai@jaguarmicro.com,
stable@dpdk.org
Subject: Re: [PATCH] hash: fix memory leak of hash_rcu_cfg
Date: Mon, 14 Nov 2022 11:03:06 +0100 [thread overview]
Message-ID: <CAJFAV8wNc10Wy5BGgQSgv9nsdMhFSSQTN+_mgZJ6ZmNyv+r1rA@mail.gmail.com> (raw)
In-Reply-To: <20221104095123.487630-1-jun.qiu@jaguarmicro.com>
On Fri, Nov 4, 2022 at 10:52 AM Jun Qiu <jun.qiu@jaguarmicro.com> wrote:
>
> The memory of h->hash_rcu_cfg which is allocated in
> rte_hash_rcu_qsbr_add was leaked.
>
> Fixes: 769b2de ("hash: implement RCU resources reclamation")
Please, use 12 chars format for commit hash, as documented.
git config alias.fixline "log -1 --abbrev=12 --format='Fixes: %h
(\"%s\")%nCc: %ae'"
> Cc: stable@dpdk.org
>
> Signed-off-by: Jun Qiu <jun.qiu@jaguarmicro.com>
Reviewed-by: David Marchand <david.marchand@redhat.com>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2022-11-14 10:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 9:51 Jun Qiu
2022-11-14 10:03 ` David Marchand [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=CAJFAV8wNc10Wy5BGgQSgv9nsdMhFSSQTN+_mgZJ6ZmNyv+r1rA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jun.qiu@jaguarmicro.com \
--cc=lei.cai@jaguarmicro.com \
--cc=stable@dpdk.org \
--cc=yipeng1.wang@intel.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;
as well as URLs for NNTP newsgroup(s).