linux-kernel - Re: [TOMOYO 1/2] tomoyo: add Documentation/tomoyo.txt

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]

Date:	Fri, 1 May 2009 22:07:31 +0900
From:	Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To:	pavel@....cz
Cc:	jmorris@...ei.org, linux-security-module@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [TOMOYO 1/2] tomoyo: add Documentation/tomoyo.txt

Sorry for delayed response.

Pavel Machek wrote:
> 2.5 Memory Allocation Rules
> 
> In TOMOYO Linux, memory allocated for holding access permissions and
> words are never freed. There is no way except rebooting the system
> that can free unneeded memory.
> 
> But don't worry. The policy seldom changes after you start production
> mode. By tuning policy before starting production mode, you can reduce
> memory usage to (usually) less than 1 MB.
> 
> ....does that mean that it leaks memory by design?

This is memory leak, but *controlled* memory allocation with a strategy for
avoiding memory fragmentation and reducing memory usage. kstrdup()ing string
data produces partially unused memory block since string data's length is
unlikely power of two. Therefore, TOMOYO allocates memory in PAGE_SIZE bytes
block and embeds string data as much as possible.
TOMOYO does not continue allocating forever.
--
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/