mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: duoming@zju.edu.cn
To: "Joe Perches" <joe@perches.com>
Cc: "Arend van Spriel" <arend.vanspriel@broadcom.com>,
	linux-kernel@vger.kernel.org,
	brcm80211-dev-list.pdl@broadcom.com, brcm80211@lists.linux.dev,
	linux-wireless@vger.kernel.org, justinstitt@google.com,
	john@keeping.me.uk, quic_alokad@quicinc.com, marcan@marcan.st,
	johannes.berg@intel.com, linus.walleij@linaro.org,
	kvalo@kernel.org
Subject: Re: [PATCH] wifi: brcm80211: handle pmk_op allocation failure
Date: Tue, 27 Feb 2024 21:44:43 +0800 (GMT+08:00)	[thread overview]
Message-ID: <62bf57d8.2291.18deacf80c6.Coremail.duoming@zju.edu.cn> (raw)
In-Reply-To: <b0a352781f58a829deadffbe2ef2085c97c6ab32.camel@perches.com>

On Tue, 27 Feb 2024 03:42:13 -0800 Joe Perches wrote:
> > > The kzalloc() in brcmf_pmksa_v3_op() will return null if the
> > > physical memory has run out. As a result, if we dereference
> > > the null value, the null pointer dereference bug will happen.
> > > 
> > > Return -ENOMEM from brcmf_pmksa_v3_op() if kzalloc() fails
> > > for pmk_op.
> > 
> > NAK (see below)
> > 
> > Also this issue was reported earlier by Joe Perches. Not sure if he 
> > wants to be mentioned as such.
> 
> I think it's unimportant to be mentioned.
> 
> I think it's more important that the code be researched
> that the simple return of -ENOMEM the appropriate fix
> and is handled by all possible callers of the function.

There are three functions that call the brcmf_pmksa_v3_op(),
including brcmf_cfg80211_set_pmksa(), brcmf_cfg80211_del_pmksa()
and brcmf_cfg80211_flush_pmksa(). The return type of the above
three functions is s32. If brcmf_pmksa_v3_op() returns -ENOMEM,
the above three functions will also return -ENOMEM. It could be
handled appropriately by the callers of the function. So I think
the simple return of -ENOMEM is appropriate.

> > > Fixes: a96202acaea4 ("wifi: brcmfmac: cfg80211: Add support for PMKID_V3 operations")
> > > Signed-off-by: Duoming Zhou <duoming@zju.edu.cn>
> > > ---
> > >   drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c | 5 +++++
> > >   1 file changed, 5 insertions(+)
> > > 
> > > diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.cq b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
> > > index 28d6a30cc01..3b420b33188 100644
> > > --- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
> > > +++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c
> > > @@ -4322,6 +4322,10 @@ brcmf_pmksa_v3_op(struct brcmf_if *ifp, struct cfg80211_pmksa *pmksa,
> > >   	int ret;
> > >   
> > >   	pmk_op = kzalloc(sizeof(*pmk_op), GFP_KERNEL);
> > > +	if (!pmk_op) {
> > > +		ret = -ENOMEM;
> > > +		goto out;
> > > +	}
> > 
> > There is really no need to introduce a new label for this. Although you 
> > can kfree() a NULL pointer there is no need to do so when you know 
> > already it is NULL. Just return -ENOMEM and be done with it.
> > 
> > Regards,
> > Arend
> > 
> > >   	pmk_op->version = cpu_to_le16(BRCMF_PMKSA_VER_3);
> > >   
> > >   	if (!pmksa) {
> > > @@ -4340,6 +4344,7 @@ brcmf_pmksa_v3_op(struct brcmf_if *ifp, struct cfg80211_pmksa *pmksa,
> > >   	pmk_op->length = cpu_to_le16(length);
> > >   
> > >   	ret = brcmf_fil_iovar_data_set(ifp, "pmkid_info", pmk_op, sizeof(*pmk_op));
> > > +out:
> > >   	kfree(pmk_op);
> > >   	return ret;
> > >   }

Best regards,
Duoming Zhou

  reply	other threads:[~2024-02-27 13:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27  8:06 Duoming Zhou
2024-02-27 11:21 ` Arend van Spriel
2024-02-27 11:42   ` Joe Perches
2024-02-27 13:44     ` duoming [this message]
2024-02-27 19:40     ` Arend van Spriel
2024-02-27 19:58       ` Joe Perches

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=62bf57d8.2291.18deacf80c6.Coremail.duoming@zju.edu.cn \
    --to=duoming@zju.edu.cn \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=joe@perches.com \
    --cc=johannes.berg@intel.com \
    --cc=john@keeping.me.uk \
    --cc=justinstitt@google.com \
    --cc=kvalo@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcan@marcan.st \
    --cc=quic_alokad@quicinc.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

all inboxes | Powered by JetHome®