linux-kernel - Re: 5.14-rc breaks iotop swap io monitoring.

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: <20210825002908.GA16064@codemonkey.org.uk>
Date:   Tue, 24 Aug 2021 20:29:08 -0400
From:   Dave Jones <davej@...emonkey.org.uk>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     Peter Zijlstra <peterz@...radead.org>,
        Linux Kernel <linux-kernel@...r.kernel.org>,
        Johannes Weiner <hannes@...xchg.org>
Subject: Re: 5.14-rc breaks iotop swap io monitoring.

On Tue, Aug 24, 2021 at 04:26:59PM -0700, Linus Torvalds wrote:
 > >  > What happens if you boot with the 'delayacct' kernel parameter.
 > >  >
 > > Yeah that boot option does make iotop work again.
 > 
 > Ok, so it's that delay allocation thing is it.
 > 
 > I'm inclined to let it be and see if somebody else notices, and how
 > big of a deal it is.
 >
 > The 'delayacct' kernel command line is an acceptable workaround if
 > this is something only a few people will even notice or care about.
 > 
 > I wonder how much people care about some statistics and iotop these days.
 > 
 > I also assume the swap stats still show up in "vmstat" etc, and that
 > it's just that iotop ended up using fancier interfaces?

afaict, vmstat is fine (though none of my machines are using swap, so
they're just reporting 0)

	Dave