From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Kalle Valo <kvalo@kernel.org>
Cc: nbd@nbd.name, lorenzo.bianconi@redhat.com,
linux-wireless@vger.kernel.org, sean.wang@mediatek.com,
deren.wu@mediatek.com
Subject: Re: [PATCH 1/2] mt76: mt7921: fix a leftover race in runtime-pm
Date: Tue, 11 Jan 2022 11:58:33 +0100 [thread overview]
Message-ID: <Yd1i2dzT7l/gLUb/@lore-desk> (raw)
In-Reply-To: <87zgo2k1b2.fsf@tynnyri.adurom.net>
[-- Attachment #1: Type: text/plain, Size: 2098 bytes --]
> Lorenzo Bianconi <lorenzo@kernel.org> writes:
>
> > Fix a possible race in mt7921_pm_power_save_work() if rx/tx napi
> > schedules ps_work and we are currently accessing device register
> > on a different cpu.
> >
> > Fixes: 1d8efc741df8 ("mt76: mt7921: introduce Runtime PM support")
> > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> > ---
> > drivers/net/wireless/mediatek/mt76/mt7921/mac.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/drivers/net/wireless/mediatek/mt76/mt7921/mac.c b/drivers/net/wireless/mediatek/mt76/mt7921/mac.c
> > index defef3496246..0744f6e42ba3 100644
> > --- a/drivers/net/wireless/mediatek/mt76/mt7921/mac.c
> > +++ b/drivers/net/wireless/mediatek/mt76/mt7921/mac.c
> > @@ -1553,6 +1553,14 @@ void mt7921_pm_power_save_work(struct work_struct *work)
> > dev->fw_assert)
> > goto out;
> >
> > + if (mutex_is_locked(&dev->mt76.mutex))
> > + /* if mt76 mutex is held we should not put the device
> > + * to sleep since we are currently accessing device
> > + * register map. We need to wait for the next power_save
> > + * trigger.
> > + */
> > + goto out;
>
> This looks fishy to me. What protects the case when ps_work is run first
> and at the same time another cpu starts accessing the registers?
>
> Do note that I didn't check the code, so I might be missing something.
before accessing chip registers, we run mt7921_mutex_acquire() so we grab mt76
mutex and run mt76_connac_pm_wake(). In mt76_connac_pm_wake() we cancel
ps_work, so it is not possible to access regs while mt7921_pm_power_save_work() is
running. The only leftover case is the other way around, i.e. if we
schedule mt7921_pm_power_save_work while we are already reading/writing chip
regs. This is only possible when mt7921_pm_power_save_work is scheduled by
rx_napi and this patch is fixing the latter case. Agree?
Regards,
Lorenzo
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2022-01-11 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-30 20:47 [PATCH 0/2] mt76: fix a leftover race in runtime-pm for mt7663/mt7921 Lorenzo Bianconi
2021-12-30 20:47 ` [PATCH 1/2] mt76: mt7921: fix a leftover race in runtime-pm Lorenzo Bianconi
2022-01-11 10:35 ` Kalle Valo
2022-01-11 10:54 ` Felix Fietkau
2022-01-11 15:00 ` Kalle Valo
2022-01-11 10:58 ` Lorenzo Bianconi [this message]
2021-12-30 20:47 ` [PATCH 2/2] mt76: mt7615: " Lorenzo Bianconi
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=Yd1i2dzT7l/gLUb/@lore-desk \
--to=lorenzo@kernel.org \
--cc=deren.wu@mediatek.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--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