[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0aa53f9c-b038-ff66-6e0e-65fe3bd3ee64@gmail.com>
Date: Wed, 23 Oct 2019 09:11:38 -0600
From: David Ahern <dsahern@...il.com>
To: Jiri Pirko <jiri@...nulli.us>, netdev@...r.kernel.org
Cc: davem@...emloft.net, jakub.kicinski@...ronome.com,
stephen@...workplumber.org, roopa@...ulusnetworks.com,
dcbw@...hat.com, nikolay@...ulusnetworks.com, mkubecek@...e.cz,
andrew@...n.ch, parav@...lanox.com, saeedm@...lanox.com,
f.fainelli@...il.com, sd@...asysnail.net, sbrivio@...hat.com,
pabeni@...hat.com, mlxsw@...lanox.com
Subject: Re: [patch iproute2-next v4 1/3] lib/ll_map: cache alternative names
On 10/19/19 11:37 AM, Jiri Pirko wrote:
> +static void ll_altname_entries_destroy(struct ll_cache *parent_im)
> +{
> + struct ll_cache *im;
> +
> + list_for_each_entry(im, &parent_im->altnames_list, altnames_list)
> + ll_entry_destroy(im, false);
you are walking a list and removing elements from it, so that should be
list_for_each_entry_safe, no?
Powered by blists - more mailing lists