linux-kernel - Re: [Libcg-devel] [RFC] How to handle the rules engine for cgroups

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]

Message-ID: <20080710171838.GA4235@linux.vnet.ibm.com>
Date:	Thu, 10 Jul 2008 22:48:38 +0530
From:	Dhaval Giani <dhaval@...ux.vnet.ibm.com>
To:	Paul Menage <menage@...gle.com>
Cc:	Vivek Goyal <vgoyal@...hat.com>,
	Peter Zijlstra <pzijlstr@...hat.com>,
	linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Libcg Devel Mailing List <libcg-devel@...ts.sourceforge.net>,
	Morton Andrew Morton <akpm@...ux-foundation.org>,
	kamezawa.hiroyu@...fujitsu.com
Subject: Re: [Libcg-devel] [RFC] How to handle the rules engine for cgroups

On Thu, Jul 10, 2008 at 09:46:46AM -0700, Paul Menage wrote:
> On Thu, Jul 10, 2008 at 7:33 AM, Vivek Goyal <vgoyal@...hat.com> wrote:
> >
> > We also need to do something to track all the forked childs after
> > the setuid, setgid or exec till original parent event got classified
> > and children need to meet the same treatment.
> 
> You'd get that automatically, since children of the task moved to the
> root cgroup (indicating "needs attention") would also end up in that
> cgroup since cgroup are inherited across fork.
> 

I am sorry, I seem to missing something, but who moves the forked
children (which got forked during the time between the parent getting
classified into the right group and the fork itself) into the correct
group?

-- 
regards,
Dhaval
--
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/