mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>,
	Duoming Zhou <duoming@zju.edu.cn>,
	linux-kernel@vger.kernel.org
Cc: 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 11:58:30 -0800	[thread overview]
Message-ID: <421ad59de37ac6bb52c95dde2e3d4bb28590ecca.camel@perches.com> (raw)
In-Reply-To: <d5ce0495-2f18-4176-90e5-7bba76132ea1@broadcom.com>

On Tue, 2024-02-27 at 20:40 +0100, Arend van Spriel wrote:
> On 2/27/2024 12:42 PM, Joe Perches wrote:
> > On Tue, 2024-02-27 at 12:21 +0100, Arend van Spriel wrote:
> > > On 2/27/2024 9:06 AM, Duoming Zhou 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.
> 
> Right. That is what I did after which I replied on Feb 18 to your email.
> 
> https://lore.kernel.org/all/3e1f11b3-a689-4c8e-bfda-b43649db7106@broadcom.com/
> 

Right, I did that as well, but I didn't look up
the entire calling tree.

It likely works.  It's also likely better than
the write through of the null pointer.

      reply	other threads:[~2024-02-27 19:58 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
2024-02-27 19:40     ` Arend van Spriel
2024-02-27 19:58       ` Joe Perches [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=421ad59de37ac6bb52c95dde2e3d4bb28590ecca.camel@perches.com \
    --to=joe@perches.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211-dev-list.pdl@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=duoming@zju.edu.cn \
    --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®