[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45de79fd-5763-bb55-22b2-0bfd64873c4f@intel.com>
Date: Mon, 9 Oct 2023 08:18:29 -0700
From: Jesse Brandeburg <jesse.brandeburg@...el.com>
To: Dan Carpenter <dan.carpenter@...aro.org>, Jinjie Ruan
<ruanjinjie@...wei.com>
CC: <intel-wired-lan@...ts.osuosl.org>, <kernel-janitors@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>, Tony Nguyen <anthony.l.nguyen@...el.com>,
Simon Horman <horms@...nel.org>, <netdev@...r.kernel.org>, Jacob Keller
<jacob.e.keller@...el.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, "David S. Miller" <davem@...emloft.net>
Subject: Re: [Intel-wired-lan] [PATCH net-next 2/2] ixgbe: fix end of loop
test in ixgbe_set_vf_macvlan()
On 10/5/2023 6:58 AM, Dan Carpenter wrote:
> The list iterator in a list_for_each_entry() loop can never be NULL.
> If the loop exits without hitting a break then the iterator points
> to an offset off the list head and dereferencing it is an out of
> bounds access.
>
> Before we transitioned to using list_for_each_entry() loops, then
> it was possible for "entry" to be NULL and the comments mention
> this. I have updated the comments to match the new code.
>
> Fixes: c1fec890458a ("ethernet/intel: Use list_for_each_entry() helper")
> Signed-off-by: Dan Carpenter <dan.carpenter@...aro.org>
Reviewed-by: Jesse Brandeburg <jesse.brandeburg@...el.com>
Powered by blists - more mailing lists