[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+ASDXPNFwvYVBMHjbTNQ-uTnQrs5TvPAH2jXgPKuFLUw2GbZA@mail.gmail.com>
Date: Tue, 26 Apr 2022 15:34:02 -0700
From: Brian Norris <briannorris@...omium.org>
To: Abhishek Kumar <kuabhs@...omium.org>
Cc: kvalo@...nel.org, quic_wgong@...cinc.com,
Linux Kernel <linux-kernel@...r.kernel.org>,
linux-wireless <linux-wireless@...r.kernel.org>,
ath10k <ath10k@...ts.infradead.org>,
"<netdev@...r.kernel.org>" <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH v2] ath10k: skip ath10k_halt during suspend for driver
state RESTARTING
On Tue, Apr 26, 2022 at 3:20 PM Abhishek Kumar <kuabhs@...omium.org> wrote:
>
> Double free crash is observed when FW recovery(caused by wmi
> timeout/crash) is followed by immediate suspend event. The FW recovery
> is triggered by ath10k_core_restart() which calls driver clean up via
> ath10k_halt(). When the suspend event occurs between the FW recovery,
> the restart worker thread is put into frozen state until suspend completes.
> The suspend event triggers ath10k_stop() which again triggers ath10k_halt()
> The double invocation of ath10k_halt() causes ath10k_htt_rx_free() to be
> called twice(Note: ath10k_htt_rx_alloc was not called by restart worker
> thread because of its frozen state), causing the crash.
...
> Tested-on: QCA6174 hw3.2 PCI WLAN.RM.4.4.1-00288-QCARMSWPZ-1
> Co-developed-by: Wen Gong <quic_wgong@...cinc.com>
> Signed-off-by: Wen Gong <quic_wgong@...cinc.com>
> Signed-off-by: Abhishek Kumar <kuabhs@...omium.org>
> ---
>
> Changes in v2:
> - Fixed typo, replaced ath11k by ath10k in the comments.
> - Adjusted the position of my S-O-B tag.
> - Added the Tested-on tag.
You could have retained my:
Reviewed-by: Brian Norris <briannorris@...omium.org>
but no worries; it's just a few characters ;)
Powered by blists - more mailing lists