From: Saeed Mahameed <saeed@kernel•org>
To: Jakob Koschel <jkl820.git@gmail•com>
Cc: Boris Pismenny <borisp@nvidia•com>,
Saeed Mahameed <saeedm@nvidia•com>,
Leon Romanovsky <leon@kernel•org>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
netdev@vger•kernel.org, linux-rdma@vger•kernel.org,
linux-kernel@vger•kernel.org,
Pietro Borrello <borrello@diag•uniroma1.it>,
Cristiano Giuffrida <c.giuffrida@vu•nl>,
"Bos, H.J." <h.j.bos@vu•nl>
Subject: Re: [PATCH net-next] net/mlx5e: avoid usage of list iterator after loop
Date: Tue, 21 Mar 2023 13:49:38 -0700 [thread overview]
Message-ID: <ZBoYYhbE7TpIOFbf@x130> (raw)
In-Reply-To: <20230301-net-mlx5e-avoid-iter-after-loop-v1-1-064c0e9b1505@gmail.com>
On 13 Mar 16:26, Jakob Koschel wrote:
>If potentially no valid element is found, 'priv_rx' would contain an
>invalid pointer past the iterator loop. To ensure 'priv_rx' is always
>valid, we only set it if the correct element was found. That allows
>adding a WARN_ON() in case the code works incorrectly, exposing
>currently undetectable potential bugs.
>
>Additionally, Linus proposed to avoid any use of the list iterator
>variable after the loop, in the attempt to move the list iterator
>variable declaration into the macro to avoid any potential misuse after
>the loop [1].
>
>Link: https://lore.kernel.org/all/CAHk-=wgRr_D8CB-D9Kg-c=EHreAsk5SqXPwr9Y7k9sA6cWXJ6w@mail.gmail.com/ [1]
>Signed-off-by: Jakob Koschel <jkl820.git@gmail•com>
Applied to net-next-mlx5.
Thanks.
prev parent reply other threads:[~2023-03-21 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 15:26 [PATCH net-next] net/mlx5e: avoid usage of list iterator after loop Jakob Koschel
2023-03-14 13:27 ` Leon Romanovsky
2023-03-21 20:49 ` Saeed Mahameed [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=ZBoYYhbE7TpIOFbf@x130 \
--to=saeed@kernel$(echo .)org \
--cc=borisp@nvidia$(echo .)com \
--cc=borrello@diag$(echo .)uniroma1.it \
--cc=c.giuffrida@vu$(echo .)nl \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=h.j.bos@vu$(echo .)nl \
--cc=jkl820.git@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=saeedm@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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