linux-kernel - Re: [v2] wifi: wlcore: sdio: Rate limit wl12xx_sdio_raw

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <170966483365.424347.18076602135809337745.kvalo@kernel.org>
Date: Tue,  5 Mar 2024 18:53:55 +0000 (UTC)
From: Kalle Valo <kvalo@...nel.org>
To: Javier Martinez Canillas <javierm@...hat.com>
Cc: linux-kernel@...r.kernel.org, Nishanth Menon <nm@...com>,
 Javier Martinez Canillas <javierm@...hat.com>,
 Breno Leitao <leitao@...ian.org>, Li Zetao <lizetao1@...wei.com>,
 linux-wireless@...r.kernel.org
Subject: Re: [v2] wifi: wlcore: sdio: Rate limit
 wl12xx_sdio_raw_{read,write}() failures warns

Javier Martinez Canillas <javierm@...hat.com> wrote:

> When these failures happen, the warning and call trace is printed which is
> excessive. Instead, just print the error but rate limited to prevent warns
> to unnecessarily pollute the kernel log buffer and make the serial console
> practically unusable.
> 
> For example, on an AM625 BeaglePlay board where accessing a SDIO WiFi chip
> fails with an -110 (ETIMEDOUT) error:
> 
>   $ dmesg | grep "sdio write\|read failed (-110)" | wc -l
>   39
> 
> Signed-off-by: Javier Martinez Canillas <javierm@...hat.com>
> Reviewed-by: Breno Leitao <leitao@...ian.org>

Patch applied to wireless-next.git, thanks.

f6e36d9e1c63 wifi: wlcore: sdio: Rate limit wl12xx_sdio_raw_{read,write}() failures warns

-- 
https://patchwork.kernel.org/project/linux-wireless/patch/20240228101042.728881-1-javierm@redhat.com/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches