public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Christos Longros <chris.longros@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] wifi: rtw89: fix wrong pci_get_drvdata type in AER handlers
Date: Thu, 9 Apr 2026 03:17:07 +0000	[thread overview]
Message-ID: <9f5dc9fa3b0747b1b07e27ac7ccf5443@realtek.com> (raw)
In-Reply-To: <20260329073857.113081-1-chris.longros@gmail.com>


Christos Longros <chris.longros@gmail.com> wrote:
> rtw89 stores an ieee80211_hw pointer via pci_set_drvdata() at probe
> time, but io_error_detected() and io_resume() retrieve it as a
> net_device pointer.  This causes netif_device_detach/attach to
> operate on an ieee80211_hw struct, reading and writing at wrong
> offsets.  The adjacent io_slot_reset() already does it correctly.
> 
> Use ieee80211_stop_queues/wake_queues instead, consistent with
> every other queue stop/start path in the driver.
> 
> Tested on RTL8852CE by calling the handlers from a test module
> before and after the fix.

Could you share the "test module" you did? I'd like to know how to
test (simulate) the io error.

> 
> Signed-off-by: Christos Longros <chris.longros@gmail.com>

Acked-by: Ping-Ke Shih <pkshih@realtek.com>



  reply	other threads:[~2026-04-09  3:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29  7:38 [PATCH] wifi: rtw89: fix wrong pci_get_drvdata type in AER handlers Christos Longros
2026-04-09  3:17 ` Ping-Ke Shih [this message]
2026-04-13  6:06   ` 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=9f5dc9fa3b0747b1b07e27ac7ccf5443@realtek.com \
    --to=pkshih@realtek.com \
    --cc=chris.longros@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    /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