From: Bruce Richardson <bruce.richardson@intel.com>
To: Jiangu Zhao <zhaojg@arraynetworks.com.cn>
Cc: helin.zhang@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] i40e: fix using memory after free issue
Date: Tue, 22 Mar 2016 15:37:45 +0000 [thread overview]
Message-ID: <20160322153744.GA20448@bricha3-MOBL3> (raw)
In-Reply-To: <1457946124-17767-1-git-send-email-zhaojg@arraynetworks.com.cn>
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
prev parent reply other threads:[~2016-03-22 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 9:02 Jiangu Zhao
2016-03-22 15:37 ` Bruce Richardson [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=20160322153744.GA20448@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=zhaojg@arraynetworks.com.cn \
/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).