bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin KaFai Lau <kafai@fb.com>
To: Hengqi Chen <hengqi.chen@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, <alan.maguire@oracle.com>
Subject: Re: BUG: Ksnoop tool failed to pass the BPF verifier with recent kernel changes
Date: Fri, 15 Oct 2021 12:30:10 -0700	[thread overview]
Message-ID: <20211015193010.22frp6eat3wz54hq@kafai-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <800ce502-8f63-8712-7ed4-d3124a5fd6fb@gmail.com>

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?

  reply	other threads:[~2021-10-15 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 16:35 BUG: Ksnoop tool failed to pass the BPF verifier with recent kernel changes Hengqi Chen
2021-10-15 19:30 ` Martin KaFai Lau [this message]
2021-10-16  9:57   ` Hengqi Chen
2021-10-18 13:53     ` Alan Maguire
2021-10-19  3:59       ` Yonghong Song

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211015193010.22frp6eat3wz54hq@kafai-mbp.dhcp.thefacebook.com \
    --to=kafai@fb.com \
    --cc=alan.maguire@oracle.com \
    --cc=bpf@vger.kernel.org \
    --cc=hengqi.chen@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).