linux-kernel - Re: nvme interrupt counters got reset after suspend/resume

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: <Z9rpeIsNlf6SBWi6@kbusch-mbp>
Date: Wed, 19 Mar 2025 09:57:44 -0600
From: Keith Busch <kbusch@...nel.org>
To: David Wang <00107082@....com>
Cc: axboe@...nel.dk, hch@....de, sagi@...mberg.me,
	linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: nvme interrupt counters got reset after suspend/resume

On Wed, Mar 19, 2025 at 11:39:10PM +0800, David Wang wrote:
> 
> This does not happend to counters for other interrupts on my system.
> Not sure whether this is designed explicitly this way, or happended to be this way to make suspend/resume work,
> or there is some bug behind this.

The nvme driver completely brings down the interrupts on suspend and
creates new ones on resume. They might have the same numbers and labels
on the other side of the resume, but they're not from the same original
allocation that tracks these stats. Hope that helps.