From: Ruan Jinjie <ruanjinjie@huawei.com>
To: Paolo Abeni <pabeni@redhat.com>, <lars.povlsen@microchip.com>,
<Steen.Hegelund@microchip.com>, <daniel.machon@microchip.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>,
<UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH net v2 3/5] net: microchip: sparx5: Fix possible memory leak in vcap_api_encode_rule_test()
Date: Tue, 12 Sep 2023 16:10:25 +0800 [thread overview]
Message-ID: <f15f3ff8-da04-ab87-a8ee-a23f5f3293c4@huawei.com> (raw)
In-Reply-To: <5eefb04c2e9028337ade88b50de3f8db3ffc5185.camel@redhat.com>
On 2023/9/12 15:38, Paolo Abeni wrote:
> On Sat, 2023-09-09 at 16:02 +0800, Jinjie Ruan wrote:
>> Inject fault while probing kunit-example-test.ko, the duprule which
>> is allocated in vcap_dup_rule() and the export which is allocated in
>
> Small typo above: 'export' should be 'eport' or 'vcap enabled port'.
> Please fix that, as it makes the changelog a bit confusing.
Thank you! I'll fix it sooner.
>
> Thanks!
>
> Paolo
>
next prev parent reply other threads:[~2023-09-12 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 8:02 [PATCH net v2 0/5] net: microchip: sparx5: Fix some memory leaks in vcap_api_kunit Jinjie Ruan
2023-09-09 8:02 ` [PATCH net v2 1/5] net: microchip: sparx5: Fix memory leak for vcap_api_rule_add_keyvalue_test() Jinjie Ruan
2023-09-09 8:02 ` [PATCH net v2 2/5] net: microchip: sparx5: Fix memory leak for vcap_api_rule_add_actionvalue_test() Jinjie Ruan
2023-09-09 8:02 ` [PATCH net v2 3/5] net: microchip: sparx5: Fix possible memory leak in vcap_api_encode_rule_test() Jinjie Ruan
2023-09-12 7:38 ` Paolo Abeni
2023-09-12 8:10 ` Ruan Jinjie [this message]
2023-09-09 8:02 ` [PATCH net v2 4/5] net: microchip: sparx5: Fix possible memory leaks in test_vcap_xn_rule_creator() Jinjie Ruan
2023-09-12 7:41 ` Paolo Abeni
2023-09-12 8:10 ` Ruan Jinjie
2023-09-09 8:02 ` [PATCH net v2 5/5] net: microchip: sparx5: Fix possible memory leaks in vcap_api_kunit Jinjie Ruan
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=f15f3ff8-da04-ab87-a8ee-a23f5f3293c4@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).