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] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240403145719.547d1083fede2cb4ca2c41ef@linux-foundation.org>
Date: Wed, 3 Apr 2024 14:57:19 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: sfr@...b.auug.org.au, kent.overstreet@...ux.dev, linux-mm@...ck.org,
 linux-kernel@...r.kernel.org, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH 1/1] lib: do limited memory accounting for modules with
 ARCH_NEEDS_WEAK_PER_CPU

On Tue,  2 Apr 2024 11:09:33 -0700 Suren Baghdasaryan <surenb@...gle.com> wrote:

> ARCH_NEEDS_WEAK_PER_CPU does not allow percpu variable definitions inside
> a function, therefore memory allocation profiling can't use it. This
> definition is used only for modules, so we still can account core kernel
> allocations and for modules we can do limited allocation accounting by
> charging all of them to a single counter. This is not ideal but better

I'll queue this as a to-be-squashed fix against "lib: add allocation
tagging support for memory allocation profiling", OK?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ