Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754607AbbBNWtU (ORCPT ); Sat, 14 Feb 2015 17:49:20 -0500 Received: from mail-qc0-f176.google.com ([209.85.216.176]:51945 "EHLO mail-qc0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754570AbbBNWtS (ORCPT ); Sat, 14 Feb 2015 17:49:18 -0500 MIME-Version: 1.0 From: Alexei Starovoitov Date: Sat, 14 Feb 2015 17:48:58 -0500 Message-ID: Subject: Re: [PATCH v3 linux-trace 1/8] tracing: attach eBPF programs to tracepoints and syscalls To: Peter Zijlstra Cc: Steven Rostedt , Ingo Molnar , Namhyung Kim , Arnaldo Carvalho de Melo , Jiri Olsa , Masami Hiramatsu , Linux API , Network Development , LKML , Linus Torvalds , "Eric W. Biederman" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 780 Lines: 20 On Wed, Feb 11, 2015 at 5:28 AM, Peter Zijlstra wrote: > > We're compiling the BPF stuff against the 'current' kernel headers > right? the tracex1 example is pulling kernel headers to demonstrate how bpf_fetch*() helpers can be used to walk kernel structures without debug info. The other examples don't need any internal headers. > So would enforcing module versioning not be sufficient? I'm going to redo the ex1 to use kprobe and some form of version check. Indeed module-like versioning should be enough. -- 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/