From: Thomas Monjalon <thomas@monjalon.net>
To: Yunjian Wang <wangyunjian@huawei.com>
Cc: dev@dpdk.org, stable@dpdk.org, honnappa.nagarahalli@arm.com,
konstantin.v.ananyev@yandex.ru, luyicai@huawei.com
Subject: Re: [dpdk-dev] [PATCH v3] ring: fix use after free in ring release
Date: Tue, 23 May 2023 12:16:31 +0200 [thread overview]
Message-ID: <3193564.aV6nBDHxoP@thomas> (raw)
In-Reply-To: <21867862766caee191228a5fe438fde899e6fd7f.1683268586.git.wangyunjian@huawei.com>
05/05/2023 08:48, Yunjian Wang:
> 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
>
> Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> Acked-by: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Applied, thanks.
That's a real pleasure to see reliability improved :)
prev parent reply other threads:[~2023-05-23 10:16 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
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 [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=3193564.aV6nBDHxoP@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=luyicai@huawei.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).