On Sun, 2017-01-01 at 09:24 +0800, Liang Guo wrote: > Package: src:linux > Version: linux-image-4.8.0-2-amd64 > Severity: serious >
I don't think this severity is justified, when the regular kernels work fine with it. > Hi, I found bpfcc-tools don't work on linux-image-4.8.0-2-amd64 and > linux-image-4.8.0-2-rt-amd64, for these kernels are signed kernel, I think > bpfcc-tools don't work on all signed kernels on x86_64 platform. bpfcc-tools > works on linux-image-4.8.0-2-amd64-unsigned, > linux-image-4.8.0-2-rt-amd64-unsigned and linux-image-4.7.0-1-amd64, following > is my detailed test log: > > ##############linux-image-4.8.0-2-amd64######################## > root@bcat:~# python /usr/share/doc/bpfcc-tools/examples/hello_world.py > bpf: Invalid argument > This seems to be the problem. I am not sure what is causing it on a signed linux package. Please also see a similar issue upstream: https://github.com/iovisor/bcc/issues/283 Going by the bug report upstream, it may not necessarily be a signed linux package issue; but I'm not sure right now. > Traceback (most recent call last): > File "/usr/share/doc/bpfcc-tools/examples/hello_world.py", line 11, in > <module> > BPF(text='int kprobe__sys_clone(void *ctx) { bpf_trace_printk("Hello, > World!\\n"); return 0; }').trace_print() > File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 203, in > __init__ > self._trace_autoload() > File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 679, in > _trace_autoload > fn = self.load_func(func_name, BPF.KPROBE) > File "/usr/lib/python2.7/dist-packages/bcc/__init__.py", line 243, in > load_func > raise Exception("Failed to load BPF program %s" % func_name) > Exception: Failed to load BPF program kprobe__sys_clone -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response
signature.asc
Description: This is a digitally signed message part
