From: Kalle Valo <kvalo@kernel•org>
To: Hector Martin <marcan@marcan•st>
Cc: "Andy Shevchenko" <andy.shevchenko@gmail•com>,
"David S. Miller" <davem@davemloft•net>,
"Jakub Kicinski" <kuba@kernel•org>,
"Rob Herring" <robh+dt@kernel•org>,
"Rafael J. Wysocki" <rafael@kernel•org>,
"Len Brown" <lenb@kernel•org>,
"Arend van Spriel" <aspriel@gmail•com>,
"Franky Lin" <franky.lin@broadcom•com>,
"Hante Meuleman" <hante.meuleman@broadcom•com>,
"Wright Feng" <wright.feng@infineon•com>,
"Dmitry Osipenko" <digetx@gmail•com>,
"Sven Peter" <sven@svenpeter•dev>,
"Alyssa Rosenzweig" <alyssa@rosenzweig•io>,
"Mark Kettenis" <kettenis@openbsd•org>,
"Rafał Miłecki" <zajec5@gmail•com>,
"Pieter-Paul Giesberts" <pieter-paul.giesberts@broadcom•com>,
"Linus Walleij" <linus.walleij@linaro•org>,
"Hans de Goede" <hdegoede@redhat•com>,
"John W. Linville" <linville@tuxdriver•com>,
"brian m. carlson" <sandals@crustytoothpaste•net>,
"open list:TI WILINK WIRELES..." <linux-wireless@vger•kernel.org>,
netdev <netdev@vger•kernel.org>,
devicetree <devicetree@vger•kernel.org>,
"Linux Kernel Mailing List" <linux-kernel@vger•kernel.org>,
"ACPI Devel Maling List" <linux-acpi@vger•kernel.org>,
"open list:BROADCOM BRCM80211 IEEE802.11n WIRELESS DRIVER"
<brcm80211-dev-list.pdl@broadcom•com>,
SHA-cyfmac-dev-list@infineon•com,
"Arend van Spriel" <arend.vanspriel@broadcom•com>,
Stable <stable@vger•kernel.org>
Subject: Re: [PATCH v4 3/9] brcmfmac: firmware: Do not crash on a NULL board_type
Date: Tue, 01 Feb 2022 07:12:57 +0200 [thread overview]
Message-ID: <8735l3dvae.fsf@kernel.org> (raw)
In-Reply-To: <c6e1bf98-55d6-1828-f19d-a3e13692da94@marcan.st> (Hector Martin's message of "Tue, 1 Feb 2022 01:53:36 +0900")
Hector Martin <marcan@marcan•st> writes:
> On 01/02/2022 01.49, Kalle Valo wrote:
>> Andy Shevchenko <andy.shevchenko@gmail•com> writes:
>>
>>> On Mon, Jan 31, 2022 at 6:07 PM Hector Martin <marcan@marcan•st> wrote:
>>>>
>>>> This unbreaks support for USB devices, which do not have a board_type
>>>> to create an alt_path out of and thus were running into a NULL
>>>> dereference.
>>>
>>> ...
>>>
>>>> @@ -599,6 +599,9 @@ static char *brcm_alt_fw_path(const char *path,
>>>> const char *board_type)
>>>> char alt_path[BRCMF_FW_NAME_LEN];
>>>> char suffix[5];
>>>>
>>>> + if (!board_type)
>>>> + return NULL;
>>>
>>> I still think it's better to have both callers do the same thing.
>>>
>>> Now it will be the double check in one case,
>>
>> I already applied a similar patch:
>>
>> https://git.kernel.org/wireless/wireless/c/665408f4c3a5
>>
>
> Feel free to drop this one from the series then, if everything else
> looks good.
Yes, I'll drop this patch 3.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-02-01 5:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 16:07 [PATCH v4 0/9] misc brcmfmac fixes (M1/T2 series spin-off) Hector Martin
2022-01-31 16:07 ` [PATCH v4 1/9] brcmfmac: pcie: Release firmwares in the brcmf_pcie_setup error path Hector Martin
2022-01-31 16:26 ` Andy Shevchenko
2022-02-01 12:27 ` Kalle Valo
2022-01-31 16:07 ` [PATCH v4 2/9] brcmfmac: firmware: Allocate space for default boardrev in nvram Hector Martin
2022-01-31 16:26 ` Andy Shevchenko
2022-01-31 16:07 ` [PATCH v4 3/9] brcmfmac: firmware: Do not crash on a NULL board_type Hector Martin
2022-01-31 16:28 ` Andy Shevchenko
2022-01-31 16:49 ` Kalle Valo
2022-01-31 16:53 ` Hector Martin
2022-02-01 5:12 ` Kalle Valo [this message]
2022-01-31 17:49 ` Andy Shevchenko
2022-01-31 16:07 ` [PATCH v4 4/9] brcmfmac: pcie: Declare missing firmware files in pcie.c Hector Martin
2022-01-31 16:07 ` [PATCH v4 5/9] brcmfmac: pcie: Replace brcmf_pcie_copy_mem_todev with memcpy_toio Hector Martin
2022-01-31 16:07 ` [PATCH v4 6/9] brcmfmac: pcie: Fix crashes due to early IRQs Hector Martin
2022-01-31 16:25 ` Andy Shevchenko
2022-01-31 16:07 ` [PATCH v4 7/9] brcmfmac: of: Use devm_kstrdup for board_type & check for errors Hector Martin
2022-01-31 22:33 ` Piotr Masłowski
2022-01-31 16:07 ` [PATCH v4 8/9] brcmfmac: fwil: Constify iovar name arguments Hector Martin
2022-01-31 16:07 ` [PATCH v4 9/9] brcmfmac: pcie: Read the console on init and shutdown Hector Martin
2022-01-31 16:25 ` Andy Shevchenko
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=8735l3dvae.fsf@kernel.org \
--to=kvalo@kernel$(echo .)org \
--cc=SHA-cyfmac-dev-list@infineon$(echo .)com \
--cc=alyssa@rosenzweig$(echo .)io \
--cc=andy.shevchenko@gmail$(echo .)com \
--cc=arend.vanspriel@broadcom$(echo .)com \
--cc=aspriel@gmail$(echo .)com \
--cc=brcm80211-dev-list.pdl@broadcom$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=digetx@gmail$(echo .)com \
--cc=franky.lin@broadcom$(echo .)com \
--cc=hante.meuleman@broadcom$(echo .)com \
--cc=hdegoede@redhat$(echo .)com \
--cc=kettenis@openbsd$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=lenb@kernel$(echo .)org \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-wireless@vger$(echo .)kernel.org \
--cc=linville@tuxdriver$(echo .)com \
--cc=marcan@marcan$(echo .)st \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pieter-paul.giesberts@broadcom$(echo .)com \
--cc=rafael@kernel$(echo .)org \
--cc=robh+dt@kernel$(echo .)org \
--cc=sandals@crustytoothpaste$(echo .)net \
--cc=stable@vger$(echo .)kernel.org \
--cc=sven@svenpeter$(echo .)dev \
--cc=wright.feng@infineon$(echo .)com \
--cc=zajec5@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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