linux-kernel - Re: [PATCH] cgroups: don't depend on CONFIG_MM

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:	Mon, 15 Sep 2008 20:56:01 +0300
From:	Pekka Enberg <penberg@...helsinki.fi>
To:	Paul Menage <menage@...gle.com>
CC:	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	balbir@...ux.vnet.ibm.com
Subject: Re: [PATCH] cgroups: don't depend on CONFIG_MM_OWNER

Hi Paul,

Paul Menage wrote:
> On Sun, Sep 14, 2008 at 10:37 AM, Pekka J Enberg <penberg@...helsinki.fi> wrote:
>> From: Pekka Enberg <penberg@...helsinki.fi>
>>
>> The revoke patches, for example, select CONFIG_MM_OWNER independently of
>> cgroups. Therefore, don't depend on CONFIG_MM_OWNER in cgroup specific code.
> 
> Yes, the existing code doesn't seem quite right - if !CONFIG_MM_OWNER
> then we don't need to even define a trivial version of
> cgroup_mm_owner_callbacks()
> 
> But your patch is too specific - tying the existance of
> cgroup_mm_owner_callbacks() to the memory controller would break other
> controllers (e.g. the memrlimit or swap controllers, which also want
> to use it)
> 
> How about:
> 
> - any cgroup that needs mm-owner callbacks selects an option
> CGROUP_MM_OWNER_CALLBACK
> 
> - CGROUP_MM_OWNER_CALLBACK selects MM_OWNER and triggers the
> definition of a non-trivial cgroup_mm_owner_callbacks() function

Yeah, sounds good to me. I just want to be able to select 
CONFIG_MM_OWNER separately for my revoke patches.

		Pekka
--
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/