From: Marco Scardovi <scardracs@disroot.org>
To: Devin Wittmayer <lucid_duck@justthetip.ca>
Cc: Felix Fietkau <nbd@nbd.name>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Ryder Lee <ryder.lee@mediatek.com>,
Deren Wu <deren.wu@mediatek.com>,
Ming Yen Hsieh <mingyen.hsieh@mediatek.com>,
Klara Modin <klarasmodin@gmail.com>,
David Gow <david@davidgow.net>,
linux-wireless@vger.kernel.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] wifi: mt76: mt792x: fix NULL pointer dereference in mt792x_init_acpi_sar_power
Date: Sat, 05 Sep 2026 07:48:50 +0200 [thread overview]
Message-ID: <oWkA8ZPAS2aI62u9I6EKqQ@disroot.org> (raw)
In-Reply-To: <20260904234838.19342-1-lucid_duck@justthetip.ca>
In data sabato 5 settembre 2026 01:48:38 Ora legale dell’Europa centrale,
Devin Wittmayer ha scritto:
> On Fri, 4 Sep 2026 18:18:26 +0200, Marco Scardovi wrote:
> > Fixes: f965333e491e ("mt76: mt7921: introduce ACPI SAR support")
>
> There is a patch for this from 25 August:
>
>
> https://lore.kernel.org/linux-wireless/20260825181712.28548-1-lucid_duck@ju
> stthetip.ca/
>
> Klara Modin reported it, David Gow confirmed the fix on a Framework 13.
>
Hi Devin,
sorry, I didn't notice that a thread was already opened so I supposed no
one reported it at all.
> One note on the Fixes tag. The crash needs a regulatory update to run
> before registration, and that only started with these:
>
> 9b80bd9cab40 2026-06-09 mt7921 regulatory wiphy self manager
> e9f3f1cc133f 2026-06-09 mt7925 regulatory wiphy self manager
>
> Before those it just set flags, so the 2022 commit would reach stable
> kernels that never had the bug.
>
You are right on that, I'll pay more attention next time
> Your trace enters through the regulatory notifier, mine through
> firmware init. I could not find mt7921_regd_notifier_work in mt76
> here, so if you have a second trigger I would like to see it.
>
The whole patch is as you see it but: I didn't add anything more.
Tbh I was working on a whole different sub but the OS refused to start
because of this one so I came up with the absolute minimum patch to
make it working
> Thanks for taking this one on.
>
> Devin
At this point you can count this patch as void. Thank you for your time,
Marco
prev parent reply other threads:[~2026-09-05 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 16:18 [PATCH] wifi: mt76: mt792x: fix NULL pointer dereference in mt792x_init_acpi_sar_power Marco Scardovi
2026-09-04 23:48 ` Devin Wittmayer
2026-09-05 5:48 ` Marco Scardovi [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=oWkA8ZPAS2aI62u9I6EKqQ@disroot.org \
--to=scardracs@disroot.org \
--cc=david@davidgow.net \
--cc=deren.wu@mediatek.com \
--cc=klarasmodin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=lucid_duck@justthetip.ca \
--cc=mingyen.hsieh@mediatek.com \
--cc=nbd@nbd.name \
--cc=ryder.lee@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.