public inbox for brcm80211@lists.linux.dev
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: Norbert van Bolhuis <nvbolhuis@gmail.com>,
	linux-wireless@vger.kernel.org,
	 Norbert van Bolhuis <norbert.vanbolhuis@ev-box.com>,
	brcm80211@lists.linux.dev
Subject: Re: [PATCH] wifi: brcmfmac: Fix oops due to NULL pointer dereference in 'brcmf_sdiod_sglist_rw'
Date: Thu, 07 Nov 2024 11:51:30 +0200	[thread overview]
Message-ID: <87iksz5q3h.fsf@kernel.org> (raw)
In-Reply-To: <a2699327-0f86-4c70-8ca4-1225f3e712d1@broadcom.com> (Arend van Spriel's message of "Thu, 7 Nov 2024 10:31:53 +0100")

Arend van Spriel <arend.vanspriel@broadcom.com> writes:

> On 11/7/2024 9:07 AM, Kalle Valo wrote:
>
>> Norbert van Bolhuis <nvbolhuis@gmail.com> writes:
>> 
>>> This patch fixes a NULL pointer dereference bug in brcmfmac that occurs
>>> when a high 'sd_sgentry_align' value applies (e.g. 512) and a lot of queued SKBs
>>> are sent from the pkt queue.
>>>
>>> The problem is the number of entries in the pre-allocated sgtable, it is
>>> nents = max(rxglom_size, txglom_size) + max(rxglom_size, txglom_size) >> 4 + 1.
>>> Given the default [rt]xglom_size=32 it's actually 35 which is too small.
>>> Worst case, the pkt queue can end up with 64 SKBs. This occurs when a new SKB
>>> is added for each original SKB if tailroom isn't enough to hold tail_pad.
>>> At least one sg entry is needed for each SKB. So, eventually the "skb_queue_walk loop"
>>> in brcmf_sdiod_sglist_rw may run out of sg entries. This makes sg_next return
>>> NULL and this causes the oops.
>> BTW it would be good to fix (in a separate patch) the sg handling so
>> that the kernel won't oops when sg entries rung. That's not really
>> robust behaviour.
>> 
>>> The patch sets nents to max(rxglom_size, txglom_size) * 2 to be able handle
>>> the worst-case.
>>> Btw. this requires only 64-35=29 * 16 (or 20 if CONFIG_NEED_SG_DMA_LENGTH) = 464
>>> additional bytes of memory.
>> s-o-b missing, please read our documentation from the link below.
>
> I have not seen the actual patch. Which mailing list was it sent to?

Only to linux-wireless, adding brcm80211 now. But the patch is in
patchwork:

https://patchwork.kernel.org/project/linux-wireless/patch/20241105204011.1603148-1-norbert.vanbolhuis@ev-box.com/

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

       reply	other threads:[~2024-11-07  9:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241105204011.1603148-1-norbert.vanbolhuis@ev-box.com>
     [not found] ` <87bjyrxy9r.fsf@kernel.org>
     [not found]   ` <a2699327-0f86-4c70-8ca4-1225f3e712d1@broadcom.com>
2024-11-07  9:51     ` Kalle Valo [this message]
2024-11-07 11:28       ` [PATCH] wifi: brcmfmac: Fix oops due to NULL pointer dereference in 'brcmf_sdiod_sglist_rw' Arend van Spriel

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=87iksz5q3h.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=brcm80211@lists.linux.dev \
    --cc=linux-wireless@vger.kernel.org \
    --cc=norbert.vanbolhuis@ev-box.com \
    --cc=nvbolhuis@gmail.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