From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: RE: [PATCH v3 06/15] acl: add allocation function attributes
Date: Fri, 24 Jan 2025 08:36:23 +0000 [thread overview]
Message-ID: <c11e7c08bbb54ce9be520c641a8bde34@huawei.com> (raw)
In-Reply-To: <20250123163003.23394-7-stephen@networkplumber.org>
> Use function attributes to catch cases where acl table is allocated
> but not freed correctly.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> lib/acl/rte_acl.h | 26 +++++++++++++++-----------
> 1 file changed, 15 insertions(+), 11 deletions(-)
>
> diff --git a/lib/acl/rte_acl.h b/lib/acl/rte_acl.h
> index ca75a6f220..b95f8778c3 100644
> --- a/lib/acl/rte_acl.h
> +++ b/lib/acl/rte_acl.h
> @@ -133,6 +133,19 @@ struct rte_acl_param {
> };
>
>
> +/** @internal opaque ACL handle */
> +struct rte_acl_ctx;
> +
> +/**
> + * De-allocate all memory used by ACL context.
> + *
> + * @param ctx
> + * ACL context to free
> + * If ctx is NULL, no operation is performed.
> + */
> +void
> +rte_acl_free(struct rte_acl_ctx *ctx);
> +
> /**
> * Create a new ACL context.
> *
> @@ -145,7 +158,8 @@ struct rte_acl_param {
> * - EINVAL - invalid parameter passed to function
> */
> struct rte_acl_ctx *
> -rte_acl_create(const struct rte_acl_param *param);
> +rte_acl_create(const struct rte_acl_param *param)
> + __rte_malloc __rte_dealloc(rte_acl_free, 1);
>
> /**
> * Find an existing ACL context object and return a pointer to it.
> @@ -160,16 +174,6 @@ rte_acl_create(const struct rte_acl_param *param);
> struct rte_acl_ctx *
> rte_acl_find_existing(const char *name);
>
> -/**
> - * De-allocate all memory used by ACL context.
> - *
> - * @param ctx
> - * ACL context to free
> - * If ctx is NULL, no operation is performed.
> - */
> -void
> -rte_acl_free(struct rte_acl_ctx *ctx);
> -
> /**
> * Add rules to an existing ACL context.
> * This function is not multi-thread safe.
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>
> 2.45.2
next prev parent reply other threads:[~2025-01-24 8:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250110170603.538756-1-stephen@networkplumber.or>
2025-01-20 23:23 ` [PATCH v2 0/3] Fix warnings when using gcc 15 Stephen Hemminger
2025-01-20 23:23 ` [PATCH v2 1/3] crypto/cnxk: fix gcc 15 warning Stephen Hemminger
2025-01-20 23:23 ` [PATCH v2 2/3] net/thunderx/base: fix build with Gcc 15 Stephen Hemminger
2025-01-20 23:23 ` [PATCH v2 3/3] examples/flow_filtering: fix gcc 15 overflow warning Stephen Hemminger
2025-01-22 10:50 ` [PATCH v2 0/3] Fix warnings when using gcc 15 David Marchand
2025-01-23 16:28 ` [PATCH v3 00/15] Add attributes to allocation functions Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 01/15] fib: add allocation function attributes Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 02/15] rib: annotate rib allocation functions Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 03/15] hash: add allocation function attributes Stephen Hemminger
2025-01-24 8:37 ` Konstantin Ananyev
2025-01-23 16:28 ` [PATCH v3 04/15] lpm: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 05/15] pipeline: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 06/15] acl: " Stephen Hemminger
2025-01-24 8:36 ` Konstantin Ananyev [this message]
2025-01-23 16:28 ` [PATCH v3 07/15] bitratestats: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 08/15] member: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 09/15] mempool: " Stephen Hemminger
2025-01-24 8:32 ` Konstantin Ananyev
2025-01-23 16:28 ` [PATCH v3 10/15] eventdev: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 11/15] ring: " Stephen Hemminger
2025-01-24 8:31 ` Konstantin Ananyev
2025-01-23 16:28 ` [PATCH v3 12/15] reorder: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 13/15] compressdev: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 14/15] telemetry: " Stephen Hemminger
2025-01-23 16:28 ` [PATCH v3 15/15] sched: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 00/16] Add " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 01/16] fib: add " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 02/16] rib: annotate rib allocation functions Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 03/16] hash: add allocation function attributes Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 04/16] lpm: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 05/16] pipeline: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 06/16] acl: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 07/16] bitratestats: " Stephen Hemminger
2025-01-24 18:14 ` [PATCH v4 08/16] member: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 09/16] mempool: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 10/16] eventdev: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 11/16] ring: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 12/16] reorder: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 13/16] compressdev: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 14/16] telemetry: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 15/16] sched: " Stephen Hemminger
2025-01-24 18:15 ` [PATCH v4 16/16] doc: add release note about allocation attributes Stephen Hemminger
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=c11e7c08bbb54ce9be520c641a8bde34@huawei.com \
--to=konstantin.ananyev@huawei.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--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).