linux-kernel - Re: Prevent inode/dentry trashing?

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: <YNX8anv2yCnkVPXy@blackbook>
Date:   Fri, 25 Jun 2021 17:55:22 +0200
From:   Michal Koutný <mkoutny@...e.com>
To:     Philipp Hahn <pmhahn+lkml@...ahn.de>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "cgroups@...r.kernel.org" <cgroups@...r.kernel.org>
Subject: Re: Prevent inode/dentry trashing?

Hello Phillip.

On Mon, Jun 07, 2021 at 02:39:35PM +0200, Philipp Hahn <pmhahn+lkml@...ahn.de> wrote:
> The trashed caches affect all other processes running in parallel or the
> first processes started each morning.
> 
> Is it possible to prevent inode/dentry trashing for example by limiting the
> cache per process(-group)?

Yes. Unless you have disabled it with CONFIG_MEMCG_KMEM or
cgroup.memory=nokmem, dentries and inodes are charged to respective
cgroups. And you can limit overall memory of a cgroup, see
memory.{max,high} attributes. (You suggest this inode/dentry consumption
is dominant enough to affect other jobs, so the limit would keep it
constrained as you intend).

HTH,
Michal

Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)