* [dpdk-dev] [PATCH] i40e: fix using memory after free issue
@ 2016-03-14 9:02 Jiangu Zhao
2016-03-22 15:37 ` Bruce Richardson
0 siblings, 1 reply; 2+ messages in thread
From: Jiangu Zhao @ 2016-03-14 9:02 UTC (permalink / raw)
To: helin.zhang; +Cc: dev
The old code still uses entry in the next loop of LIST_FOREACH after free() in i40e_res_pool_destroy().
Change to a safe way to free entry, which is similar with LIST_FOREACH_SAFE in FreeBSD.
Signed-off-by: Jiangu Zhao <zhaojg@arraynetworks.com.cn>
---
drivers/net/i40e/i40e_ethdev.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/net/i40e/i40e_ethdev.c b/drivers/net/i40e/i40e_ethdev.c
index 2f676f6..5af2128 100644
--- a/drivers/net/i40e/i40e_ethdev.c
+++ b/drivers/net/i40e/i40e_ethdev.c
@@ -3317,17 +3317,21 @@ i40e_res_pool_init (struct i40e_res_pool_info *pool, uint32_t base,
static void
i40e_res_pool_destroy(struct i40e_res_pool_info *pool)
{
- struct pool_entry *entry;
+ struct pool_entry *entry, *next_entry;
if (pool == NULL)
return;
- LIST_FOREACH(entry, &pool->alloc_list, next) {
+ for (entry = LIST_FIRST(&pool->alloc_list);
+ entry && (next_entry = LIST_NEXT(entry, next), 1);
+ entry = next_entry) {
LIST_REMOVE(entry, next);
rte_free(entry);
}
- LIST_FOREACH(entry, &pool->free_list, next) {
+ for (entry = LIST_FIRST(&pool->free_list);
+ entry && (next_entry = LIST_NEXT(entry, next), 1);
+ entry = next_entry) {
LIST_REMOVE(entry, next);
rte_free(entry);
}
--
1.8.3.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-dev] [PATCH] i40e: fix using memory after free issue
2016-03-14 9:02 [dpdk-dev] [PATCH] i40e: fix using memory after free issue Jiangu Zhao
@ 2016-03-22 15:37 ` Bruce Richardson
0 siblings, 0 replies; 2+ messages in thread
From: Bruce Richardson @ 2016-03-22 15:37 UTC (permalink / raw)
To: Jiangu Zhao; +Cc: helin.zhang, dev
On Mon, Mar 14, 2016 at 09:02:04AM +0000, Jiangu Zhao wrote:
> The old code still uses entry in the next loop of LIST_FOREACH after free() in i40e_res_pool_destroy().
> Change to a safe way to free entry, which is similar with LIST_FOREACH_SAFE in FreeBSD.
>
> Signed-off-by: Jiangu Zhao <zhaojg@arraynetworks.com.cn>
Thanks for the patch. It's missing a "fixes" line as descripted here:
http://dpdk.org/doc/guides/contributing/patches.html#commit-messages-body
so can you perhaps reply with the id of the commit this is fixing, (or add it
into the commit message if you end up doing a V2 of the patch)
Helin, can you perhaps review this patch as i40e maintainer.
> ---
> drivers/net/i40e/i40e_ethdev.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/i40e/i40e_ethdev.c b/drivers/net/i40e/i40e_ethdev.c
> index 2f676f6..5af2128 100644
> --- a/drivers/net/i40e/i40e_ethdev.c
> +++ b/drivers/net/i40e/i40e_ethdev.c
> @@ -3317,17 +3317,21 @@ i40e_res_pool_init (struct i40e_res_pool_info *pool, uint32_t base,
> static void
> i40e_res_pool_destroy(struct i40e_res_pool_info *pool)
> {
> - struct pool_entry *entry;
> + struct pool_entry *entry, *next_entry;
>
> if (pool == NULL)
> return;
>
> - LIST_FOREACH(entry, &pool->alloc_list, next) {
> + for (entry = LIST_FIRST(&pool->alloc_list);
> + entry && (next_entry = LIST_NEXT(entry, next), 1);
> + entry = next_entry) {
Can we use LIST_FOREACH_SAFE?
/Bruce
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-03-22 15:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-14 9:02 [dpdk-dev] [PATCH] i40e: fix using memory after free issue Jiangu Zhao
2016-03-22 15:37 ` Bruce Richardson
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).