Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Eason Lai (賴易聖)" <Eason.Lai@mediatek.com>
To: "nbd@nbd.name" <nbd@nbd.name>,
	"lorenzo@kernel.org" <lorenzo@kernel.org>,
	"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
	"Mingyen Hsieh (謝明諺)" <Mingyen.Hsieh@mediatek.com>
Cc: "Allan Wang (王家偉)" <Allan.Wang@mediatek.com>,
	"Eric-SY Chang (張書源)" <Eric-SY.Chang@mediatek.com>,
	"Deren Wu (武德仁)" <Deren.Wu@mediatek.com>,
	"Ryder Lee" <Ryder.Lee@mediatek.com>,
	"Quan Zhou (周全)" <Quan.Zhou@mediatek.com>,
	"Michael.Lo@mediatek.com" <Michael.Lo@mediatek.com>,
	"Shayne Chen (陳軒丞)" <Shayne.Chen@mediatek.com>,
	"Sean Wang" <Sean.Wang@mediatek.com>,
	"Leon Yen (顏良儒)" <Leon.Yen@mediatek.com>,
	"KM Lin (林昆民)" <km.lin@mediatek.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] wifi: mt76: mt7921: Add PCIe AER handler support to prevent system crash
Date: Tue, 14 Jul 2026 01:21:33 +0000	[thread overview]
Message-ID: <14b59de82b480725e920452e941f4ab6efacae21.camel@mediatek.com> (raw)
In-Reply-To: <d7eb196b01003a1de70456d5a31d9b4a37d555bd.camel@sipsolutions.net>

On Wed, 2025-10-08 at 11:12 +0200, Johannes Berg wrote:
> Hi,
> 
> So ... yeah it's your driver, and yes it's already at v2, but ...
> this
> still seems very much papering over a problem?
> 
> On Wed, 2025-10-08 at 16:59 +0800, Mingyen Hsieh wrote:
> > 
> > Unable to handle kernel paging request at virtual address
> > ffffffc01099eac0
> > pc : mt76_dma_add_buf+0x124/0x188 [mt76]
> 
> Why does it even crash there?
> 

It's an out-of-range access: the HW returned an unexpected value that
wasn't validated before use.

v3 posted here:
https://lore.kernel.org/linux-wireless/20260506070458.3096180-1-jb.tsai@mediatek.com/

Thanks,
Eason

> > +++ b/drivers/net/wireless/mediatek/mt76/agg-rx.c
> > @@ -96,6 +96,9 @@ mt76_rx_aggr_reorder_work(struct work_struct
> > *work)
> >  	struct sk_buff_head frames;
> >  	int nframes;
> >  
> > +	if (atomic_read(&dev->bus_hung) == 1)
> > +		return;
> 
> And how does sprinkling this "magic dust" all over even do anything?
> 
> 
> This sounds a bit like the driver isn't able to deal with surprise
> removal, what happens if you e.g. rmmod it while running traffic? I
> believe the effect of the error recovery would be similar, if you
> don't
> handle it, so are you sure there's not a completely different
> underlying
> bug?
> 
> johannes




      reply	other threads:[~2026-07-14  1:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08  8:59 [PATCH v2] wifi: mt76: mt7921: Add PCIe AER handler support to prevent system crash Mingyen Hsieh
2025-10-08  9:12 ` Johannes Berg
2026-07-14  1:21   ` Eason Lai (賴易聖) [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=14b59de82b480725e920452e941f4ab6efacae21.camel@mediatek.com \
    --to=eason.lai@mediatek.com \
    --cc=Allan.Wang@mediatek.com \
    --cc=Deren.Wu@mediatek.com \
    --cc=Eric-SY.Chang@mediatek.com \
    --cc=Leon.Yen@mediatek.com \
    --cc=Michael.Lo@mediatek.com \
    --cc=Mingyen.Hsieh@mediatek.com \
    --cc=Quan.Zhou@mediatek.com \
    --cc=Ryder.Lee@mediatek.com \
    --cc=Sean.Wang@mediatek.com \
    --cc=Shayne.Chen@mediatek.com \
    --cc=johannes@sipsolutions.net \
    --cc=km.lin@mediatek.com \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lorenzo@kernel.org \
    --cc=nbd@nbd.name \
    /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