linux-kernel - Re: [PATCH v2] cgroup/cpuset: call fmeter_init() when cpuset.memory

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: <CA+B+MYQuz9ue1ZogpEGb8J+F8UA5P0dD-R1cRUp-4EgDBnPS+Q@mail.gmail.com>
Date: Fri, 14 Feb 2025 18:04:18 +0800
From: Jin Guojie <guojie.jin@...il.com>
To: Michal Koutný <mkoutny@...e.com>
Cc: Waiman Long <longman@...hat.com>, cgroups@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] cgroup/cpuset: call fmeter_init() when
 cpuset.memory_pressure disabled

On Wed, Jan 15, 2025 at 7:01 PM Michal Koutný <mkoutny@...e.com> wrote:
>
> On Wed, Jan 15, 2025 at 01:05:21PM +0800, Jin Guojie <guojie.jin@...il.com> wrote:
> > V2:
> > * call fmeter_init() when writing 0 to the memory_pressure_enabled
>
> Thanks for taking into account the feedback.
>
> I'm still curious -- is this:
>         a) a new LTP test,
>         b) a new failure,
>         c) an old failure, new look
> or anything else?

For the three situations a, b, and c you mentioned, none of them is true.
In fact, this "case cpuset_memory_pressure" has been in LTP for a long time,
and the same error will occur when running in multiple kernel versions.

The method to reproduce the error is provided in the description of patch v1.

https://lore.kernel.org/cgroups/CA+B+MYRNsdKcYxC8kbyzVrdH9fT8c2if5UxGguKep36ZHe6HMQ@mail.gmail.com/T/#u

The fmeter_getrate() function in the kernel has not been modified for
a long time,
so currently LTP "case cpuset_memory_pressure" still produces the same error.

>
> Michal