From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jan Seiffert <kaffeemonster@googlemail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Matt Evans <matt@ozlabs.org>
Subject: Re: [REGRESSION][PATCH] bpf_jit drops the ball on indirect negative mem references
Date: Wed, 28 Mar 2012 22:05:29 +0200 [thread overview]
Message-ID: <1332965129.2325.12.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAPwCz79wO=5zTZmCG+ePfRuEu-p_Vosi18bYZ-MVNZGOdbE3aQ@mail.gmail.com>
On Wed, 2012-03-28 at 21:15 +0200, Jan Seiffert wrote:
> Consider the following test program:
>
> #include <stdio.h>
> #include <sys/types.h>
> #include <sys/socket.h>
> #include <netinet/in.h>
> #include <pcap-bpf.h>
>
> #define die(x) do {perror(x); return 1;} while (0)
> struct bpf_insn udp_filter[] = {
> /* 0 */ BPF_STMT(BPF_LDX|BPF_W|BPF_IMM, -1048576+(0)), /* leax net[0] */
> /* 1 */ BPF_STMT(BPF_LD|BPF_B|BPF_IND, 0), /* ldb [x+0] */
> /* 2 */ BPF_STMT(BPF_RET|BPF_A, 0), /* ret a */
> };
When this point was raised some weeks ago, we wanted to see a _real_ use
of negative mem reference.
You provide a test program but what this filter is supposed to do
exactly ?
next prev parent reply other threads:[~2012-03-28 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 19:15 [REGRESSION][PATCH] bpf_jit drops the ball on indirect negative mem references Jan Seiffert
2012-03-28 20:05 ` Eric Dumazet [this message]
2012-03-28 20:26 ` Jan Seiffert
2012-03-28 20:39 ` Eric Dumazet
2012-03-29 11:54 ` Jan Seiffert
2012-03-29 13:57 ` Eric Dumazet
2012-03-30 9:11 ` Eric Dumazet
2012-03-30 13:42 ` Jan Seiffert
2012-03-30 14:08 ` Eric Dumazet
2012-03-30 14:11 ` Josh Boyer
2012-03-30 15:24 ` Matt Evans
2012-03-30 15:19 ` Matt Evans
2012-03-30 15:51 ` Jan Seiffert
2012-03-28 20:58 ` David Miller
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=1332965129.2325.12.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=kaffeemonster@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@ozlabs.org \
--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