| 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
| ||
|
Date: Wed, 17 Feb 2010 12:43:12 +0900 From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> To: "Leonidas ." <leonidas137@...il.com> Cc: linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: Notification when a task is created/exits On Wed, 17 Feb 2010 08:46:51 +0530 "Leonidas ." <leonidas137@...il.com> wrote: \ > > 2. implement cgroup subsystem > > AFAIK, in the latest kernel, cgroup subsystem can be implemented as module. > > cgroup has fork/exit handler. > > And you can implement some useful controls for tasks you watch via > > cgroup's control interface. > > > > This sounds close to what I have in mind, but unfortunately I dont > have any idea what is cgroup > subsystem. How to implement cgroup subsystem? Can you give pointers to > some existing code > or document? Documentation/cgroup/*.txt Maybe cpuacct cgroup in kernel/sche.c or device cgroup in security/device_cgroup.c is portable size, but they are not module. block/blk-cgroup is module and maybe in readable size. > Also, using this mechanism can we monitor each thread created in > user space? I.e. it is only a fork handler or even a > pthread_create/clone can be tracked this way. > please read documents. I think you can. Thanks, -Kame -- 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/
Powered by blists - more mailing lists