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  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:	Sun, 07 Sep 2008 21:03:24 +0530
From:	Balbir Singh <>
To:	Paul Menage <>
CC:	KAMEZAWA Hiroyuki <>,
	Daisuke Nishimura <>,
	Andrew Morton <>,
	Hugh Dickins <>,
	Li Zefan <>,,
Subject: Re: [PATCH][mmotm]memcg: handle null dereference of mm->owner

Paul Menage wrote:
> On Fri, Sep 5, 2008 at 1:40 AM, KAMEZAWA Hiroyuki
> <> wrote:
>> BTW, I have a question to Balbir and Paul. (I'm sorry I missed the discussion.)
>> Recently I wonder why we need MM_OWNER.
>> - What's bad with thread's cgroup ?
> Because lots of mm operations take place in a context where we don't
> have a thread pointer, and hence no cgroup.

Right, Thanks! Allocating memory is not that big a problem (we usually know the
context), while freeing memory, we can't assume that current is freeing it

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists