Re: [PATCH v3] ath10k: add flag to protect napi operation to avoid dead loop hang

2020-12-14 Thread Kalle Valo
Ben Greear writes: > On 12/9/20 1:24 AM, Kalle Valo wrote: >> Wen Gong writes: >> >>> On 2020-09-08 00:22, Kalle Valo wrote: >>> Just like with the recent firmware restart patch, isn't ar->napi_enabled racy? Wouldn't test_and_set_bit() and test_and_clear_bit() be safer?

[ath6kl:ath11k-qca6390-bringup] BUILD SUCCESS WITH WARNING 60fad49a69e7b2f896ce7b1ade4ed532227b8e22

2020-12-14 Thread kernel test robot
dma_addr_t-aka-unsigned-int |-- nios2-allyesconfig | `-- drivers-net-wireless-ath-ath11k-qmi.c:warning:format-llx-expects-argument-of-type-long-long-unsigned-int-but-argument-has-type-dma_addr_t-aka-unsigned-int |-- nios2-randconfig-r035-20201214 | `-- drivers-net-wireless-ath-ath11k-qmi.c:warning:format-l

Re: CVE-2020-3702: Firmware updates for ath9k and ath10k chips

2020-12-14 Thread Jouni Malinen
On Mon, Dec 07, 2020 at 03:04:38PM +0100, Pali Rohár wrote: > Hello! Has somebody fixes this security issue in ath9k driver? About > 4 months passed and if this issue is not fixed, could you please share > at least incomplete / WIP patches? I would like to look at it and have > this issue finally f

[ath6kl:ath11k-qca6390-bringup 11/27] drivers/net/wireless/ath/ath11k/qmi.c:1680:46: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 4 has type 'dma_addr_t' {aka

2020-12-14 Thread kernel test robot
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git ath11k-qca6390-bringup head: 60fad49a69e7b2f896ce7b1ade4ed532227b8e22 commit: 7d4892f101fc6bcd3cecbdfc7419a4a2bf6bb58b [11/27] ath11k: qmi: print allocated memory segment addresses and sizes config: nios2-allyesconfig (attach