From: Bert Karwatzki <spasswolf@web.de>
To: Mike Lothian <mike@fireburn.co.uk>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
sean.wang@kernel.org, nbd@nbd.name, lorenzo.bianconi@redhat.com,
sean.wang@mediatek.com, deren.wu@mediatek.com,
mingyen.hsieh@mediatek.com, linux-wireless@vger.kernel.org,
linux-mediatek@lists.infradead.org, spasswolf@web.de
Subject: Re: [PATCH] wifi: mt76: mt7921: fix null pointer access in mt792x_mac_link_bss_remove
Date: Wed, 28 Aug 2024 10:17:20 +0200 [thread overview]
Message-ID: <980698e0d6dfa1e0043edfed6e174ff17705e053.camel@web.de> (raw)
In-Reply-To: <CAHbf0-HYi=x11bc-sMJFbZ4cbkdphMYQ_hjzD_wrPvJevVwyYg@mail.gmail.com>
Am Mittwoch, dem 28.08.2024 um 00:38 +0100 schrieb Mike Lothian:
> But not the follow on fix which fixes suspend...
>
> diff --git a/drivers/net/wireless/mediatek/mt76/mt7921/main.c
> b/drivers/net/wireless/mediatek/mt76/mt7921/main.c
> index 2e6268cb06c0..a85c19da77e5 100644
> --- a/drivers/net/wireless/mediatek/mt76/mt7921/main.c
> +++ b/drivers/net/wireless/mediatek/mt76/mt7921/main.c
> @@ -1182,7 +1182,7 @@ static void mt7921_ipv6_addr_change(struct
> ieee80211_hw *hw,
> struct inet6_dev *idev)
> {
> struct mt792x_vif *mvif = (struct mt792x_vif *)vif->drv_priv;
> - struct mt792x_dev *dev = mvif->phy->dev;
> + struct mt792x_dev *dev = mt792x_hw_dev(hw);
> struct inet6_ifaddr *ifa;
> struct in6_addr ns_addrs[IEEE80211_BSS_ARP_ADDR_LIST_LEN];
> struct sk_buff *skb;
> @@ -1205,6 +1205,9 @@ static void mt7921_ipv6_addr_change(struct
> ieee80211_hw *hw,
> },
> };
>
> + if (!mvif->phy)
> + return;
> +
> read_lock_bh(&idev->lock);
> list_for_each_entry(ifa, &idev->addr_list, if_list) {
> if (ifa->flags & IFA_F_TENTATIVE)
>
> > > >
> >
That is interesting (or odd) because suspend (s2idle) works for me in next-
20240827 on this hardware:
04:00.0 Network controller [0280]: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz
[14c3:0608]
are you using a different model?
[ 272.780054] [ T848] wlp4s0: deauthenticating from 54:67:51:3d:a2:d2 by
local choice (Reason: 3=DEAUTH_LEAVING)
[ 273.067438] [ T3437] PM: suspend entry (s2idle)
[ 273.151140] [ T3437] Filesystems sync: 0.083 seconds
[ 273.157029] [ T3437] Freezing user space processes
Can your the post the backtrace of your error (when commit 479ffee68d59c599f is
applied)?
Bert Karwatzki
next prev parent reply other threads:[~2024-08-28 8:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 23:46 [PATCH] wifi: mt76: mt7921: fix null pointer access in mt792x_mac_link_bss_remove sean.wang
2024-07-19 11:26 ` Bert Karwatzki
2024-07-24 9:36 ` Linux regression tracking (Thorsten Leemhuis)
2024-07-29 10:51 ` Bert Karwatzki
2024-07-29 13:49 ` Linux regression tracking (Thorsten Leemhuis)
2024-08-01 12:38 ` Mike Lothian
2024-08-01 16:57 ` Bert Karwatzki
2024-08-27 16:30 ` Mike Lothian
2024-08-27 21:13 ` Bert Karwatzki
2024-08-27 23:38 ` Mike Lothian
2024-08-28 8:17 ` Bert Karwatzki [this message]
2024-08-28 15:20 ` Mike Lothian
2024-08-28 17:05 ` Bert Karwatzki
2024-08-29 16:35 ` Mike Lothian
2024-08-29 16:52 ` Mike Lothian
2024-09-05 13:33 ` Kalle Valo
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=980698e0d6dfa1e0043edfed6e174ff17705e053.camel@web.de \
--to=spasswolf@web.de \
--cc=deren.wu@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=mike@fireburn.co.uk \
--cc=mingyen.hsieh@mediatek.com \
--cc=nbd@nbd.name \
--cc=regressions@lists.linux.dev \
--cc=sean.wang@kernel.org \
--cc=sean.wang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox