linux-kernel - Re: failed to remove key (0, ce:ce:1e:27:bb:e0) from hardware (-110) (ETIMEDOUT)

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <877cbqcjzw.fsf@kernel.org>
Date: Thu, 05 Sep 2024 16:23:15 +0300
From: Kalle Valo <kvalo@...nel.org>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: Baochen Qiang <quic_bqiang@...cinc.com>,  James Prestwood
 <prestwoj@...il.com>,  linux-wireless@...r.kernel.org,
  ath10k@...ts.infradead.org,  LKML <linux-kernel@...r.kernel.org>
Subject: Re: failed to remove key (0, ce:ce:1e:27:bb:e0) from hardware
 (-110) (ETIMEDOUT)

Paul Menzel <pmenzel@...gen.mpg.de> writes:

> Am 04.09.24 um 16:48 schrieb Kalle Valo:
>> Paul Menzel writes:
>
>>> Linux 6.11-rc6+ logged the warning below when resuming from ACPI S3
>>> (or unloading and loading the `ath10k_core`/`ath10k_pci` modules)
>>> having been connected to an AVM network:
>>>
>>>      wlp58s0: failed to remove key (0, ce:ce:1e:27:bb:e0) from hardware (-110)
>>>
>>> Error code 110 is the value for ETIMEDOUT. I saw James patch [1], and
>>> applied it, and the error is still there (as expected).
>>>
>>> Can the warning be improved so the user know, which component is at fault?
>> The warning comes from mac80211 and it already contains your network
>> interface name (wlp58s0). What else would you want to see?
>
> As an ignorant user, I do not know what to do with the warning. I’d
> like to see a suggestion how to get rid of the warning. Maybe:
>
>     wlp58s0: failed to remove key (0, ce:ce:1e:27:bb:e0) from hardware
>     in X s (-110), please report it to the vendor firmware

The warning can come due to different reasons in different drivers, it's
not really easy to identify what the user should do.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

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