On Wed, Jul 17, 2019 at 10:51:43PM -0400, Joel Fernandes wrote: > Hi Alexei, > > On Wed, Jul 17, 2019 at 02:40:42PM -0700, Alexei Starovoitov wrote: > > On Wed, Jul 17, 2019 at 6:01 AM Joel Fernandes <joel@xxxxxxxxxxxxxxxxx> wrote: > > > > I trimmed cc. some emails were bouncing. > > Ok, thanks. > > > > > I think allowing one tracepoint and disallowing another is pointless > > > > from security point of view. Tracing bpf program can do bpf_probe_read > > > > of anything. > > > > > > I think the assumption here is the user controls the program instructions at > > > runtime, but that's not the case. The BPF program we are loading is not > > > dynamically generated, it is built at build time and it is loaded from a > > > secure verified partition, so even though it can do bpf_probe_read, it is > > > still not something that the user can change. > > > > so you're saying that by having a set of signed bpf programs which > > instructions are known to be non-malicious and allowed set of tracepoints > > to attach via selinux whitelist, such setup will be safe? > > Have you considered how mix and match will behave? > > Do you mean the effect of mixing tracepoints and programs? I have not > considered this. I am Ok with further enforcing of this (only certain > tracepoints can be attached to certain programs) if needed. What do > you think? We could have a new bpf(2) syscall attribute specify which > tracepoint is expected, or similar. > > I wanted to walk you through our 2 usecases we are working on: thanks for sharing the use case details. Appreciate it. > 1. timeinstate: By hooking 2 programs onto sched_switch and cpu_frequency > tracepoints, we are able to collect CPU power per-UID (specific app). Connor > O'Brien is working on that. > > 2. inode to file path mapping: By hooking onto VFS tracepoints we are adding to > the android kernels, we can collect data when the kernel resolves a file path > to a inode/device number. A BPF map stores the inode/dev number (key) and the > path (value). We have usecases where we need a high speed lookup of this > without having to scan all the files in the filesystem. Can you share the link to vfs tracepoints you're adding? Sounds like you're not going to attempt to upstream them knowing Al's stance towards them? May be there is a way we can do the feature you need, but w/o tracepoints? > For the first usecase, the BPF program will be loaded and attached to the > scheduler and cpufreq tracepoints at boot time and will stay attached > forever. This is why I was saying having a daemon to stay alive all the time > is pointless. However, if since you are completely against using tracefs > which it sounds like, then we can do a daemon that is always alive. As I said earlier this use case can be solved by pinning raw_tp object into bpffs. Such patches are welcomed. > For the second usecase, the program attach is needed on-demand unlike the > first usecase, and then after the usecase completes, it is detached to avoid > overhead. > > For the second usecase, privacy is important and we want the data to not be > available to any process. So we want to make sure only selected processes can > attach to that tracepoint. This is the reason why I was doing working on > these patches which use the tracefs as well, since we get that level of > control. It's hard to recommend anything w/o seeing the actual tracepoints you're adding to vfs and type of data bpf program extracts from there. Sounds like it's some sort of cache of inode->file name ? If so, why is it privacy related?
