Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Stefan Dösinger" <stefan@codeweavers.com>
To: linux-wireless@vger.kernel.org,
	Arend van Spriel <arend.vanspriel@broadcom.com>
Subject: Re: [PATCH] wifi: brcmfmac: Check the return value of of_property_read_string_index
Date: Mon, 06 Jan 2025 14:22:29 +0300	[thread overview]
Message-ID: <4619776.LvFx2qVVIh@grey> (raw)
In-Reply-To: <058aba76-817c-480a-9404-38b030325890@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 1528 bytes --]

Am Montag, 6. Januar 2025, 14:02:17 Ostafrikanische Zeit schrieb Arend van 
Spriel:
> On 1/6/2025 11:37 AM, Stefan Dösinger wrote:
> > Somewhen between 6.10 and 6.11 the driver started to crash on my
> > MacBookPro14,3. The property doesn't exist and 'tmp' remains
> > uninitialized, so we pass a random pointer to devm_kstrdup().
> 
> By the looks of it this is an intel-based platform. Is that correct? So
> does it have a devicetree? I would expect the root node find to fail,
> but apparently is does not. Strange though that root node does not have
> a compatible property. Anyway, the analysis looks sane so ...

Yes, this is an Intel based MacBook Pro - the 2017 version.

I was curious about the same thing and tried to find out where it expects to 
get those properties from. I didn't find a definitive answer and concluded 
that it reads the properties from somewhere on the wifi cards ROM rather than 
the computer's firmware / ACPI Tabes / whatever. If you can tell me where I 
should look I can see if I find out more.

If you think it is helpful or might point towards deeper issues I can try do a 
bisect for whatever patch broke this. I vaguely suspect though that it was 
always broken but by random luck a NULL pointer happened to be on the stack in 
the right place.

> No need to use 'err'. You can directly do
> of_property_read_string_index() in the if statement below.

Check, I'll resend. I found both styles in use (though admittedly reusing 
'err' to print it to dmesg).

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2025-01-06 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 10:37 [PATCH] wifi: brcmfmac: Check the return value of of_property_read_string_index Stefan Dösinger
2025-01-06 11:02 ` Arend van Spriel
2025-01-06 11:22   ` Stefan Dösinger [this message]
2025-01-06 18:53     ` Stefan Dösinger

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=4619776.LvFx2qVVIh@grey \
    --to=stefan@codeweavers.com \
    --cc=arend.vanspriel@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    /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