From: "Eelco Chaudron" <echaudro@redhat.com>
To: "Alexei Starovoitov" <alexei.starovoitov@gmail.com>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
Xdp <xdp-newbies@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Jesper Dangaard Brouer" <brouer@redhat.com>
Subject: Re: Capture xdp packets in an fentry BPF hook
Date: Thu, 20 Feb 2020 14:17:41 +0100 [thread overview]
Message-ID: <0B0D36B7-283E-468A-8DE1-C733FD9A9896@redhat.com> (raw)
In-Reply-To: <20200219203626.ozkdoyhyexwxwbbt@ast-mbp>
On 19 Feb 2020, at 21:36, Alexei Starovoitov wrote:
> On Wed, Feb 19, 2020 at 03:38:40PM +0100, Eelco Chaudron wrote:
>> Hi Alexei at al.,
>>
>> I'm getting closer to finally have an xdpdump tool that uses the bpf
>> fentry/fexit tracepoints, but I ran into a final hurdle...
>>
>> To stuff the packet into a perf ring I'll need to use the
>> bpf_perf_event_output(), but unfortunately, this is a program of
>> trace type,
>> and not XDP so the packet data is not added automatically :(
>>
>> Secondly even trying to pass the actual packet data as a reference to
>> bpf_perf_event_output() will not work as the verifier wants the data
>> to be
>> on the fp.
>>
>> Even worse, the trace program gets the XDP info not thought the ctx,
>> but
>> trough the fentry/fexit input value, i.e.:
>>
>> SEC("fentry/func")
>> int BPF_PROG(trace_on_entry, struct xdp_buff *xdp)...
>>
>> struct net_device {
>> int ifindex;
>> } __attribute__((preserve_access_index));
>>
>> struct xdp_rxq_info {
>> struct net_device *dev;
>> __u32 queue_index;
>> } __attribute__((preserve_access_index));
>>
>> struct xdp_buff {
>> void *data;
>> void *data_end;
>> void *data_meta;
>> void *data_hard_start;
>> unsigned long handle;
>> struct xdp_rxq_info *rxq;
>> } __attribute__((preserve_access_index));
>>
>> Hence even trying to copy in bytes to a local buffer is not allowed
>> by the
>> verifier, i.e. __u8 *data = (u8 *)(long)xdp->data;
>>
>> Can you let me know how you envisioned a BPF entry hook to capture
>> packets
>> from XDP. Am I missing something, or is there something missing from
>> the
>> infrastructure?
>
> Tracing of XDP is missing a helper similar to bpf_skb_output() for
> skb.
> Its first arg will be 'struct xdp_buff *' and .arg1_type =
> ARG_PTR_TO_BTF_ID
> then it will work similar to bpf_skb_output() in progs/kfree_skb.c.
Thanks for clarifying the needs for a new helper. I will be on PTO next
week but will work on a bpf_xdp_output() helper when I get back.
Cheers,
Eelco
prev parent reply other threads:[~2020-02-20 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 14:38 Capture xdp packets in an fentry BPF hook Eelco Chaudron
2020-02-19 20:36 ` Alexei Starovoitov
2020-02-19 22:14 ` Toke Høiland-Jørgensen
2020-02-19 22:20 ` Alexei Starovoitov
2020-02-19 22:34 ` Toke Høiland-Jørgensen
2020-02-20 13:17 ` Eelco Chaudron [this message]
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=0B0D36B7-283E-468A-8DE1-C733FD9A9896@redhat.com \
--to=echaudro@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=toke@redhat.com \
--cc=xdp-newbies@vger.kernel.org \
/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).