Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755456AbbFMCjU (ORCPT ); Fri, 12 Jun 2015 22:39:20 -0400 Received: from mail-pd0-f180.google.com ([209.85.192.180]:35268 "EHLO mail-pd0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753721AbbFMCjR (ORCPT ); Fri, 12 Jun 2015 22:39:17 -0400 From: Alexei Starovoitov To: "David S. Miller" Cc: Andy Lutomirski , Ingo Molnar , Steven Rostedt , Wang Nan , lizefan@huawei.com, Daniel Wagner , Daniel Borkmann , linux-api@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2 net-next 0/3] bpf: share helpers between tracing and networking Date: Fri, 12 Jun 2015 19:39:11 -0700 Message-Id: <1434163154-5218-1-git-send-email-ast@plumgrid.com> X-Mailer: git-send-email 1.7.9.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1300 Lines: 33 v1->v2: switched to init_user_ns from current_user_ns as suggested by Andy Introduce new helpers to access 'struct task_struct'->pid, tgid, uid, gid, comm fields in tracing and networking. Share bpf_trace_printk() and bpf_get_smp_processor_id() helpers between tracing and networking. Alexei Starovoitov (3): bpf: introduce current->pid, tgid, uid, gid, comm accessors bpf: allow networking programs to use bpf_trace_printk() for debugging bpf: let kprobe programs use bpf_get_smp_processor_id() helper include/linux/bpf.h | 4 +++ include/uapi/linux/bpf.h | 19 +++++++++++++ kernel/bpf/core.c | 7 +++++ kernel/bpf/helpers.c | 58 ++++++++++++++++++++++++++++++++++++++ kernel/trace/bpf_trace.c | 28 ++++++++++++------ net/core/filter.c | 8 ++++++ samples/bpf/bpf_helpers.h | 6 ++++ samples/bpf/tracex2_kern.c | 24 ++++++++++++---- samples/bpf/tracex2_user.c | 67 ++++++++++++++++++++++++++++++++++++++------ 9 files changed, 199 insertions(+), 22 deletions(-) -- 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/