Re: BUG: Ksnoop tool failed to pass the BPF verifier with recent kernel changes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Oct 14, 2021 at 12:35:42AM +0800, Hengqi Chen wrote:
> Hi, BPF community,
> 
> 
> I would like to report a possible bug in bpf-next,
> hope I don't make any stupid mistake. Here is the details:
> 
> I have two VMs:
> 
> One has the kernel built against the following commit:
> 
> 0693b27644f04852e46f7f034e3143992b658869 (bpf-next)
> 
> The ksnoop tool (from BCC repo) works well on this VM.
> 
> 
> Another has the kernel built against the following commit:
> 
> 5319255b8df9271474bc9027cabf82253934f28d (bpf-next)
> 
> On this VM, the ksnoop tool failed with the following message:
I see the error in both mentioned bpf-next commits above.
I use the latest llvm and bcc from github.

Can you confirm which llvm version (or llvm git commit) you are using
in both the good and the bad case?



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux