linux-kernel - Re: Anybody interested in a kernel memory manager?

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] [day] [month] [year] [list]

Date:	Thu, 02 Oct 2008 09:58:00 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Gregor Rebel <linux@...lbarrier.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Anybody interested in a kernel memory manager?

Gregor Rebel wrote:
> I'm currently writing two modules related to XEN.

What are you working on, out of curiosity?

> Both modules need to
> acquire dynamic memory (via __get_free_pages() and kmalloc() ).
> In order to reuse some code, I wrote a third module which can provide
> simple memory-services to other modules:
> * Allocated pages and memories of each client-module gets tracked
> * When a module is about to exit, it can issue one function call to
> release all of its memories
> * Before first using the memory manager, each module has to obtain a
> unique owner id number by calling a registration function
> * by loading the memory manager with a debug argument, memory
> allocations automatically get logged into syslog facility
>
> I know, that currently each module keeps track of its memory allocations
> on its own.
>
> Is there a general interest to have such a memory manager in the kernel?

The best way to get a useful response is to post the patches and see 
what happens.  There's no way to really evaluate what you're proposing 
in the abstract.

    J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/