linux-kernel - Re: [PATCH v5] selftests: cgroup: add tests to verify the zswap writeback path

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: <CAKEwX=MhxjUsOq+W2Tf1fdc5O-oyPUBdsct1-Df8VQf8-Q2TuQ@mail.gmail.com>
Date: Wed, 8 May 2024 11:41:50 -0700
From: Nhat Pham <nphamcs@...il.com>
To: Usama Arif <usamaarif642@...il.com>
Cc: akpm@...ux-foundation.org, hannes@...xchg.org, yosryahmed@...gle.com, 
	chengming.zhou@...ux.dev, linux-mm@...ck.org, linux-kernel@...r.kernel.org, 
	kernel-team@...a.com
Subject: Re: [PATCH v5] selftests: cgroup: add tests to verify the zswap
 writeback path

On Wed, May 8, 2024 at 10:14 AM Usama Arif <usamaarif642@...il.com> wrote:
>
> Attempt writeback with the below steps and check using
> memory.stat.zswpwb if zswap writeback occurred:
> 1. Allocate memory.
> 2. Reclaim memory equal to the amount that was allocated in step 1.
>    This will move it into zswap.
> 3. Save current zswap usage.
> 4. Move the memory allocated in step 1 back in from zswap.
> 5. Set zswap.max to half the amount that was recorded in step 3.
> 6. Attempt to reclaim memory equal to the amount that was allocated,
>    this will either trigger writeback if it's enabled, or reclamation
>    will fail if writeback is disabled as there isn't enough zswap
>    space.
>
> Suggested-by: Nhat Pham <nphamcs@...il.com>
> Signed-off-by: Usama Arif <usamaarif642@...il.com>
> Acked-by: Yosry Ahmed <yosryahmed@...gle.com>

Thanks for adding this test, Usama!

Acked-by: Nhat Pham <nphamcs@...il.com>