-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kernel config read failed, error:Config not found #117
Comments
Can old version works? like v0.1.10 . I think that cfc4n@vm-server:~$ cat /boot/config-`uname -r`|grep CONFIG_BPF
CONFIG_BPF=y
CONFIG_BPF_LSM=y
CONFIG_BPF_SYSCALL=y
CONFIG_BPF_JIT_ALWAYS_ON=y
CONFIG_BPF_JIT_DEFAULT_ON=y
# CONFIG_BPF_PRELOAD is not set
CONFIG_BPFILTER=y
CONFIG_BPFILTER_UMH=m
CONFIG_BPF_JIT=y
CONFIG_BPF_STREAM_PARSER=y
CONFIG_BPF_EVENTS=y
CONFIG_BPF_KPROBE_OVERRIDE= |
0.1.10 works, here is my kernel config, I suspect commit egrep 'BPF|BTF' /usr/src/bpf-next/.config
|
maybe. but , why is this ? |
my kernel is custom build, I don't have
ls -l /boot/conf* old kernel config from centos distro
my custom running kernel [root@centos-dev ecapture]# uname -a
|
@cfc4n to resolve my problem, I found the fix with diff below, my custom kernel has config located here
|
wait...
|
I could not find official documentation yet, according to my understanding, when I build custom kernel from kernel source, the ls -l /lib/modules/
this is for my centos 8 with custom kernel build I also checked ubuntu 22.04 machine that is upgraded from ubuntu 20.04, so the kernel is upgraded from the distro, I don't have custom kernel build on this machine, but it has the same symbolic link ls -l /lib/modules/
it seems to be safe to assume |
I think I speak too early, the fix i mentioned only fix ecapture running in the host VM machine, if I put the ecapture in container like netshoot pod, it failed to run with same error. so the fix is not good, ecapture 0.1.10 works in container fine. maybe we need to think about if the |
please wait, I'm release new version. something need to debug.. |
fyi, i recompiled the kernel with
|
there is problem with the code,
the second problem i found when I hacked the code to bypass line 47 |
yes ,the code here is flawed. I'll send a PR later. That is my fault, thannnnkkkksssss. |
Signed-off-by: CFC4N <cfc4n.cs@gmail.com>
pkg : fix Kernel config read failed, error:Config not found #117
@cfc4n I am sorry to tell you that I tested again with your fix #123, it did not fix the problem on my VM with custom kernel build with
also I am concerned even if we fixed now my workaround is to replace |
eh.... That is scene I didn't expect while use on k8s container. I'll try a new idea. |
maybe add a new flag switch or something like that for andriod environment, restore the previous behavior that worked in container environment? |
I don't think so. |
remove detection of BPF config when running at container. In Github Action release.yml , qemu in docker ,do not have BPF config , eCapture cant works with ecapture -h. other issue : #117 Signed-off-by: CFC4N <cfc4n.cs@gmail.com>
Describe the bug
the most recent ecapture build from master branch breaks with error
To Reproduce
Steps to reproduce the behavior:
Expected behavior
should work
Screenshots
Linux Server/Android (please complete the following information):
Additional context
ecapture works before on this same machine with same kernel build
The text was updated successfully, but these errors were encountered: