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: Thu, 23 Jun 2016 17:13:26 -0400 From: Tejun Heo <tj@...nel.org> To: Daniel Borkmann <daniel@...earbox.net> Cc: Martin KaFai Lau <kafai@...com>, cgroups@...r.kernel.org, linux-kernel@...r.kernel.org, netdev@...r.kernel.org, Alexei Starovoitov <ast@...com>, kernel-team@...com Subject: Re: [PATCH net-next v2 2/4] cgroup: bpf: Add BPF_MAP_TYPE_CGROUP_ARRAY Hello, On Thu, Jun 23, 2016 at 11:42:31AM +0200, Daniel Borkmann wrote: > I presume it's a valid use case to pin a cgroup map, put fds into it and > remove the pinned file expecting to continue to match on it, right? So > lifetime is really until last prog using a cgroup map somewhere gets removed > (even if not accessible from user space anymore, meaning no prog has fd and > pinned file was removed). Yeap, from what I can see, the cgroup will stay around (even if it gets deleted) as long as the bpf rule using it is around and that's completely fine from cgroup side. Thanks. -- tejun
Powered by blists - more mailing lists