linux-kernel - Re: [PATCH 1/1] net: spacemit: Check netif_carrier

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 for Android: free password hash cracker in your pocket

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

Message-ID: <e3890633-351d-401d-abb1-5b2625c2213b@iscas.ac.cn>
Date: Mon, 19 Jan 2026 11:54:44 +0800
From: Vivian Wang <wangruikang@...as.ac.cn>
To: Chukun Pan <amadeus@....edu.cn>
Cc: Yixun Lan <dlan@...too.org>, Paolo Abeni <pabeni@...hat.com>,
 Jakub Kicinski <kuba@...nel.org>, Eric Dumazet <edumazet@...gle.com>,
 Andrew Lunn <andrew+netdev@...n.ch>, "David S . Miller"
 <davem@...emloft.net>, linux-riscv@...ts.infradead.org,
 linux-kernel@...r.kernel.org, spacemit@...ts.linux.dev,
 netdev@...r.kernel.org
Subject: Re: [PATCH 1/1] net: spacemit: Check netif_carrier_ok when reading
 stats

Hi Cunkun Pan:

On 1/18/26 18:00, Chukun Pan wrote:
> Currently, when the interface is not linked up, reading the interface
> stats will print several timeout logs. Add a netif_carrier_ok check to
> the emac_stats_update function to avoid this situation:

I am unable to reproduce this problem.

Can you elaborate on what you mean by "not linked up"? I couldn't
reproduce this on an unconnected interface.

I would also appreciate more information on this in general - full
kernel logs, hardware information (which board, what you were doing with
cables, etc...)

Thanks,
Vivian "dramforever" Wang