All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Kalle Valo <kvalo@kernel.org>,
	"marcin.slusarz@gmail.com" <marcin.slusarz@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Marcin Ślusarz" <mslusarz@renau.com>,
	"Larry Finger" <Larry.Finger@lwfinger.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw88: schedule rx work after everything is set up
Date: Tue, 28 May 2024 02:50:50 +0000	[thread overview]
Message-ID: <13e848c1544245e6aef4b89c3f38daf0@realtek.com> (raw)
In-Reply-To: <87jzjf8990.fsf@kernel.org>

Kalle Valo <kvalo@kernel.org> wrote:
> marcin.slusarz@gmail.com writes:
> 
> > From: Marcin Ślusarz <mslusarz@renau.com>
> >
> > Right now it's possible to hit NULL pointer dereference in
> > rtw_rx_fill_rx_status on hw object and/or its fields because
> > initialization routine can start getting USB replies before
> > rtw_dev is fully setup.
> >
> > The stack trace looks like this:
> >
> > rtw_rx_fill_rx_status
> > rtw8821c_query_rx_desc
> > rtw_usb_rx_handler
> > ...
> > queue_work
> > rtw_usb_read_port_complete
> > ...
> > usb_submit_urb
> > rtw_usb_rx_resubmit
> > rtw_usb_init_rx
> > rtw_usb_probe
> >
> > So while we do the async stuff rtw_usb_probe continues and calls
> > rtw_register_hw, which does all kinds of initialization (e.g.
> > via ieee80211_register_hw) that rtw_rx_fill_rx_status relies on.
> >
> > Fix this by moving the first usb_submit_urb after everything
> > is set up.
> >
> > For me, this bug manifested as:
> > [    8.893177] rtw_8821cu 1-1:1.2: band wrong, packet dropped
> > [    8.910904] rtw_8821cu 1-1:1.2: hw->conf.chandef.chan NULL in rtw_rx_fill_rx_status
> > because I'm using Larry's backport of rtw88 driver with the NULL
> > checks in rtw_rx_fill_rx_status.
> >
> > This should fix:
> > https://marc.info/?l=linux-wireless&m=167907688311943&w=2
> 
> Please use permalinks from lore.kernel.org, marc links don't contain the
> Message-Id and are hence unreliable.
> 

Use tags below: 

Reported-by: Tim K <tpkuester@gmail.com>
Closes: https://lore.kernel.org/linux-wireless/CA+shoWQ7P49jhQasofDcTdQhiuarPTjYEDa--NiVVx494WcuQw@mail.gmail.com/




  reply	other threads:[~2024-05-28  2:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27 17:01 [PATCH] wifi: rtw88: schedule rx work after everything is set up marcin.slusarz
2024-05-27 17:17 ` Kalle Valo
2024-05-28  2:50   ` Ping-Ke Shih [this message]
2024-05-28  3:00     ` Ping-Ke Shih
2024-05-28 11:02     ` Marcin Ślusarz
2024-05-29  1:28       ` Ping-Ke Shih
2024-05-30 14:33         ` Tim K
2024-05-31  0:35           ` Ping-Ke Shih
2024-07-02  3:15           ` Ping-Ke Shih
2024-07-05  1:45       ` Ping-Ke Shih

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=13e848c1544245e6aef4b89c3f38daf0@realtek.com \
    --to=pkshih@realtek.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=marcin.slusarz@gmail.com \
    --cc=mslusarz@renau.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.