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: Tue, 6 Mar 2018 11:35:31 +0100 From: Peter Zijlstra <peterz@...radead.org> To: Daniel Borkmann <daniel@...earbox.net> Cc: Alexei Starovoitov <ast@...nel.org>, davem@...emloft.net, torvalds@...ux-foundation.org, mingo@...nel.org, rostedt@...dmis.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, kernel-team@...com, linux-api@...r.kernel.org Subject: Re: [PATCH bpf-next 0/5] bpf, tracing: introduce bpf raw tracepoints On Mon, Mar 05, 2018 at 02:36:07PM +0100, Daniel Borkmann wrote: > On 03/01/2018 05:19 AM, Alexei Starovoitov wrote: > > This patch set is a different way to address the pressing need to access > > task_struct pointers in sched tracepoints from bpf programs. > > > > The first approach simply added these pointers to sched tracepoints: > > https://lkml.org/lkml/2017/12/14/753 > > which Peter nacked. > > Few options were discussed and eventually the discussion converged on > > doing bpf specific tracepoint_probe_register() probe functions. > > Details here: > > https://lkml.org/lkml/2017/12/20/929 > > Ping, Peter/Steven. If you have a chance, please review the series. This series doesn't really touch anything I maintain, but the general appraoch seems sane to me. I like the first patch that ensures structures are passed by reference. The rest is all tracepoint/bpf glue and I never really got into the bpf internals, so I don't think I've got anything useful to say there.
Powered by blists - more mailing lists