From: Eric Dumazet <eric.dumazet@gmail.com>
To: Daniel Borkmann <dborkman@redhat.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH v3 net-next 4/4] filter: add minimal BPF JIT emitted image disassembler
Date: Tue, 19 Mar 2013 09:43:10 -0700 [thread overview]
Message-ID: <1363711390.2558.20.camel@edumazet-glaptop> (raw)
In-Reply-To: <1363711172-9728-5-git-send-email-dborkman@redhat.com>
On Tue, 2013-03-19 at 17:39 +0100, Daniel Borkmann wrote:
> This is a minimal stand-alone user space helper, that allows for debugging or
> verification of emitted BPF JIT images. This is in particular useful for
> emitted opcode debugging, since minor bugs in the JIT compiler can be fatal.
> The disassembler is architecture generic and uses libopcodes and libbfd.
>
> How to get to the disassembly, example:
>
> 1) `echo 2 > /proc/sys/net/core/bpf_jit_enable`
> 2) Load a BPF filter (e.g. `tcpdump -p -n -s 0 -i eth1 host 192.168.20.0/24`)
> 3) Run e.g. `bpf_jit_disasm -o` to disassemble the most recent JIT code output
>
> `bpf_jit_disasm -o` will display the related opcodes to a particular instruction
> as well. Example for x86_64:
>
> $./bpf_jit_disasm
> 94 bytes emitted from JIT compiler (pass:3, flen:9)
> ffffffffa0356000 + <x>:
> 0: push %rbp
> 1: mov %rsp,%rbp
> 4: sub $0x60,%rsp
> 8: mov %rbx,-0x8(%rbp)
> c: mov 0x68(%rdi),%r9d
> 10: sub 0x6c(%rdi),%r9d
> 14: mov 0xe0(%rdi),%r8
> 1b: mov $0xc,%esi
> 20: callq 0xffffffffe0d01b71
> 25: cmp $0x86dd,%eax
> 2a: jne 0x000000000000003d
> 2c: mov $0x14,%esi
> 31: callq 0xffffffffe0d01b8d
> 36: cmp $0x6,%eax
> [...]
> 5c: leaveq
> 5d: retq
>
> $ ./bpf_jit_disasm -o
> 94 bytes emitted from JIT compiler (pass:3, flen:9)
> ffffffffa0356000 + <x>:
> 0: push %rbp
> 55
> 1: mov %rsp,%rbp
> 48 89 e5
> 4: sub $0x60,%rsp
> 48 83 ec 60
> 8: mov %rbx,-0x8(%rbp)
> 48 89 5d f8
> c: mov 0x68(%rdi),%r9d
> 44 8b 4f 68
> 10: sub 0x6c(%rdi),%r9d
> 44 2b 4f 6c
> [...]
> 5c: leaveq
> c9
> 5d: retq
> c3
>
> Cc: Eric Dumazet <edumazet@google.com>
> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
> ---
> scripts/bpf_jit_disasm.c | 216 +++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 216 insertions(+)
> create mode 100644 scripts/bpf_jit_disasm.c
Acked-by: Eric Dumazet <edumazet@google.com>
next prev parent reply other threads:[~2013-03-19 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 16:39 [PATCH v3 net-next 0/4] net: filter: BPF updates Daniel Borkmann
2013-03-19 16:39 ` [PATCH v3 net-next 1/4] flow_keys: include thoff into flow_keys for later usage Daniel Borkmann
2013-03-19 16:41 ` Eric Dumazet
2013-03-20 16:15 ` David Miller
2013-03-19 16:39 ` [PATCH v3 net-next 2/4] net: flow_dissector: add __skb_get_poff to get a start offset to payload Daniel Borkmann
2013-03-19 16:42 ` Eric Dumazet
2013-03-20 17:16 ` David Miller
2013-03-19 16:39 ` [PATCH v3 net-next 3/4] filter: add ANC_PAY_OFFSET instruction for loading payload start offset Daniel Borkmann
2013-03-19 16:42 ` Eric Dumazet
2013-03-20 17:16 ` David Miller
2013-03-19 16:39 ` [PATCH v3 net-next 4/4] filter: add minimal BPF JIT emitted image disassembler Daniel Borkmann
2013-03-19 16:43 ` Eric Dumazet [this message]
2013-03-20 17:17 ` David Miller
2013-03-20 18:57 ` Daniel Borkmann
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=1363711390.2558.20.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=edumazet@google.com \
--cc=netdev@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