From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: Yunjian Wang <wangyunjian@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "konstantin.v.ananyev@yandex.ru" <konstantin.v.ananyev@yandex.ru>,
"luyicai@huawei.com" <luyicai@huawei.com>,
"stable@dpdk.org" <stable@dpdk.org>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: RE: [dpdk-dev] [PATCH v2] ring: fix use after free in ring release
Date: Thu, 20 Apr 2023 16:56:37 +0000 [thread overview]
Message-ID: <DBAPR08MB5814BA950BDA0909C66433B398639@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <c23b1135e1b0676ef7d82969b39a21df992d418f.1681972694.git.wangyunjian@huawei.com>
> -----Original Message-----
> From: Yunjian Wang <wangyunjian@huawei.com>
> Sent: Thursday, April 20, 2023 1:44 AM
> To: dev@dpdk.org
> Cc: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>;
> konstantin.v.ananyev@yandex.ru; luyicai@huawei.com; Yunjian Wang
> <wangyunjian@huawei.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH v2] ring: fix use after free in ring release
>
> After the memzone is freed, it is not removed from the 'rte_ring_tailq'.
> If rte_ring_lookup is called at this time, it will cause a use-after-free problem.
> This change prevents that from happening.
>
> Fixes: 4e32101f9b01 ("ring: support freeing")
> Cc: stable@dpdk.org
>
> Suggested-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
This is incorrect, this is not a suggestion from me. Please remove this.
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
Other than the above, the patch looks fine.
Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> ---
> v2: update code suggested by Honnappa Nagarahalli
> ---
> lib/ring/rte_ring.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/lib/ring/rte_ring.c b/lib/ring/rte_ring.c index
> 8ed455043d..2755323b8a 100644
> --- a/lib/ring/rte_ring.c
> +++ b/lib/ring/rte_ring.c
> @@ -333,11 +333,6 @@ rte_ring_free(struct rte_ring *r)
> return;
> }
>
> - if (rte_memzone_free(r->memzone) != 0) {
> - RTE_LOG(ERR, RING, "Cannot free memory\n");
> - return;
> - }
> -
> ring_list = RTE_TAILQ_CAST(rte_ring_tailq.head, rte_ring_list);
> rte_mcfg_tailq_write_lock();
>
> @@ -354,6 +349,9 @@ rte_ring_free(struct rte_ring *r)
>
> TAILQ_REMOVE(ring_list, te, next);
>
> + if (rte_memzone_free(r->memzone) != 0)
> + RTE_LOG(ERR, RING, "Cannot free memory\n");
> +
> rte_mcfg_tailq_write_unlock();
>
> rte_free(te);
> --
> 2.33.0
next prev parent reply other threads:[~2023-04-20 16:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 13:11 [dpdk-dev] [PATCH] " Yunjian Wang
2023-04-18 23:53 ` Honnappa Nagarahalli
2023-04-19 7:08 ` wangyunjian
2023-04-19 21:44 ` Honnappa Nagarahalli
2023-04-20 6:48 ` wangyunjian
2023-04-20 6:43 ` [dpdk-dev] [PATCH v2] " Yunjian Wang
2023-04-20 16:56 ` Honnappa Nagarahalli [this message]
2023-05-01 12:32 ` Konstantin Ananyev
2023-05-01 19:06 ` Honnappa Nagarahalli
2023-05-02 23:06 ` Konstantin Ananyev
2023-05-03 5:44 ` Honnappa Nagarahalli
2023-05-03 22:32 ` Konstantin Ananyev
2023-05-03 23:45 ` Honnappa Nagarahalli
2023-05-05 1:26 ` wangyunjian
2023-05-05 6:48 ` [dpdk-dev] [PATCH v3] " Yunjian Wang
2023-05-23 10:16 ` Thomas Monjalon
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=DBAPR08MB5814BA950BDA0909C66433B398639@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=luyicai@huawei.com \
--cc=nd@arm.com \
--cc=stable@dpdk.org \
--cc=wangyunjian@huawei.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).