From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Ma Ke <make_ruc2021@163.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <shannon.nelson@amd.com>,
<sd@queasysnail.net>, <u.kleine-koenig@baylibre.com>,
<mdf@kernel.org>
Subject: Re: [PATCH] net: ethernet: fix NULL dereference in nixge_recv()
Date: Wed, 11 Dec 2024 10:28:13 +0100 [thread overview]
Message-ID: <cb9e64fa-f47e-4e6b-9f98-8832e5acbf73@intel.com> (raw)
In-Reply-To: <20241211083424.2580563-1-make_ruc2021@163.com>
On 12/11/24 09:34, Ma Ke wrote:
> In function nixge_recv() dereference of NULL pointer priv->rx_bd_v is
> possible for the case of its allocation failure in netdev_priv(ndev).
please be more precise about the case, rx_bd_v is not set during
netdev(w/priv) allocation
the embedded priv part is allocated together with the netdev, in the
.probe()
>
> Move while() loop with priv->rx_bd_v dereference under the check for
> its validity.
this style has some benefits, but in the kernel we prefer the early
return:
if (!priv->rx_bd_v)
return 0;
instead of touching a whole function
>
> Cc: stable@vger.kernel.org
> Fixes: 492caffa8a1a ("net: ethernet: nixge: Add support for National Instruments XGE netdev")
> Signed-off-by: Ma Ke <make_ruc2021@163.com>
> ---
> drivers/net/ethernet/ni/nixge.c | 86 ++++++++++++++++-----------------
> 1 file changed, 43 insertions(+), 43 deletions(-)
next prev parent reply other threads:[~2024-12-11 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 8:34 [PATCH] net: ethernet: fix NULL dereference in nixge_recv() Ma Ke
2024-12-11 9:28 ` Przemek Kitszel [this message]
2024-12-11 13:57 ` Andrew Lunn
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=cb9e64fa-f47e-4e6b-9f98-8832e5acbf73@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=make_ruc2021@163.com \
--cc=mdf@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=shannon.nelson@amd.com \
--cc=stable@vger.kernel.org \
--cc=u.kleine-koenig@baylibre.com \
/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