| From | Andy Lutomirski <> | Date | Fri, 27 Jun 2014 17:16:41 -0700 | Subject | Re: [PATCH RFC net-next 03/14] bpf: introduce syscall(BPF, ...) and BPF maps |
| |
On Fri, Jun 27, 2014 at 5:05 PM, Alexei Starovoitov <ast@plumgrid.com> wrote: > BPF syscall is a demux for different BPF releated commands. > > 'maps' is a generic storage of different types for sharing data between kernel > and userspace. > > The maps can be created/deleted from user space via BPF syscall: > - create a map with given id, type and attributes > map_id = bpf_map_create(int map_id, map_type, struct nlattr *attr, int len) > returns positive map id or negative error > > - delete map with given map id > err = bpf_map_delete(int map_id) > returns zero or negative error
What's the scope of "id"? How is it secured?
This question is brought to you by keyctl, which is terminally fucked. At some point I'll generate some proof of concept exploits for severe bugs caused by misdesign of a namespace.
--Andy
|