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

Message-ID: <349dba2d.b878.195af373591.Coremail.00107082@163.com>
Date: Thu, 20 Mar 2025 00:23:05 +0800 (CST)
From: "David Wang" <00107082@....com>
To: "Keith Busch" <kbusch@...nel.org>
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

Hi, 

At 2025-03-19 23:57:44, "Keith Busch" <kbusch@...nel.org> wrote:
>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.

Copy that~!  And thanks for clearing things out.



David