Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1560585
| From | Michal Hocko <mhocko@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: Potential issues (security and otherwise) with the current cgroup-bpf API |
| Date | 2017-01-17 14:30 +0100 |
| Message-ID | <t0BZM-7Ce-21@gated-at.bofh.it> (permalink) |
| References | (5 earlier) <sQhJ0-7iB-11@gated-at.bofh.it> <sQhSF-7lQ-3@gated-at.bofh.it> <sQoKu-3Gs-23@gated-at.bofh.it> <sVuvT-4Rn-5@gated-at.bofh.it> <t047L-1vN-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Sun 15-01-17 20:19:01, Tejun Heo wrote: [...] > So, what's proposed is a proper part of bpf. In terms of > implementation, cgroup helps by hosting the pointers but that doesn't > necessarily affect the conceptual structure of it. Given that, I > don't think it'd be a good idea to add anything to cgroup interface > for this feature. Introspection is great to have but this should be > introspectable together with other bpf programs using the same > mechanism. That's where it belongs. If BPF only piggy backs on top of cgroup to iterate tasks shouldn't we at least enforce that the cgroup has to be a leaf one and no further children groups can be created once there is BPF program attached? This should break the existing usecases AFAIU and it would allow future changes without major API surprises. -- Michal Hocko SUSE Labs
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: Potential issues (security and otherwise) with the current cgroup-bpf API Michal Hocko <mhocko@kernel.org> - 2017-01-17 14:30 +0100
Re: Potential issues (security and otherwise) with the current cgroup-bpf API Peter Zijlstra <peterz@infradead.org> - 2017-01-17 14:40 +0100
Re: Potential issues (security and otherwise) with the current cgroup-bpf API Michal Hocko <mhocko@kernel.org> - 2017-01-17 15:20 +0100
Re: Potential issues (security and otherwise) with the current cgroup-bpf API Andy Lutomirski <luto@amacapital.net> - 2017-01-17 21:40 +0100
Re: Potential issues (security and otherwise) with the current cgroup-bpf API Tejun Heo <tj@kernel.org> - 2017-01-18 23:30 +0100
Re: Potential issues (security and otherwise) with the current cgroup-bpf API Michal Hocko <mhocko@kernel.org> - 2017-01-19 10:10 +0100
csiph-web