From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"dpdk-dev" <dev@dpdk.org>, "Jerin Jacob" <jerinj@marvell.com>
Subject: Re: [dpdk-dev] packet data access bug in bpf and pdump libs
Date: Wed, 9 Oct 2019 17:20:58 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35C60B6A@smartserver.smartshare.dk> (raw)
In-Reply-To: <20191009081442.3e7f1af4@hermes.lan>
> -----Original Message-----
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Wednesday, October 9, 2019 5:15 PM
>
> On Wed, 9 Oct 2019 17:06:24 +0200
> Morten Brørup <mb@smartsharesystems.com> wrote:
>
> > > -----Original Message-----
> > > From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> > > Sent: Wednesday, October 9, 2019 5:02 PM
> > >
> > > On Wed, 9 Oct 2019 11:11:46 +0000
> > > "Ananyev, Konstantin" <konstantin.ananyev@intel.com> wrote:
> > >
> > > > Hi Morten,
> > > >
> > > > >
> > > > > Hi Konstantin and Stephen,
> > > > >
> > > > > I just noticed the same bug in your bpf and pcap libraries:
> > > > >
> > > > > You are using rte_pktmbuf_mtod(), but should be using
> > > rte_pktmbuf_read(). Otherwise you cannot read data across multiple
> > > segments.
> > > >
> > > > In plain data buffer mode expected input for BPF program is start
> of
> > > first segment packet data.
> > > > Other segments are simply not available to BPF program in that
> mode.
> > > > AFAIK, cBPF uses the same model.
> > > >
> > > > >
> > > > >
> > > > > Med venlig hilsen / kind regards
> > > > > - Morten Brørup
> > > >
> > >
> > > For packet capture, the BPF program is only allowed to look at
> first
> > > segment.
> > > pktmbuf_read is expensive and can cause a copy.
> >
> > It is only expensive if going beyond the first segment:
> >
> > static inline const void *rte_pktmbuf_read(const struct rte_mbuf *m,
> > uint32_t off, uint32_t len, void *buf)
> > {
> > if (likely(off + len <= rte_pktmbuf_data_len(m)))
> > return rte_pktmbuf_mtod_offset(m, char *, off);
> > else
> > return __rte_pktmbuf_read(m, off, len, buf);
> > }
>
> But it would mean potentially big buffer on the stack (in case)
No, the buffer only needs to be the size of the accessed data. I use it like this:
char buffer[sizeof(uint32_t)];
for (;; pc++) {
switch (pc->code) {
case BPF_LD_ABS_32:
p = rte_pktmbuf_read(m, pc->k, sizeof(uint32_t), buffer);
if (unlikely(p == NULL)) return 0; /* Attempting to read beyond packet. Bail out. */
a = rte_be_to_cpu_32(*(const uint32_t *)p);
continue;
case BPF_LD_ABS_16:
p = rte_pktmbuf_read(m, pc->k, sizeof(uint16_t), buffer);
if (unlikely(p == NULL)) return 0; /* Attempting to read beyond packet. Bail out. */
a = rte_be_to_cpu_16(*(const uint16_t *)p);
continue;
next prev parent reply other threads:[~2019-10-09 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 11:03 Morten Brørup
2019-10-09 11:11 ` Ananyev, Konstantin
2019-10-09 11:35 ` Morten Brørup
2019-10-09 15:02 ` Stephen Hemminger
2019-10-09 15:06 ` Morten Brørup
2019-10-09 15:14 ` Stephen Hemminger
2019-10-09 15:20 ` Morten Brørup [this message]
2019-10-09 17:24 ` Stephen Hemminger
2019-10-10 7:29 ` Morten Brørup
2019-10-10 15:36 ` Ananyev, Konstantin
2019-10-11 8:01 ` Morten Brørup
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=98CBD80474FA8B44BF855DF32C47DC35C60B6A@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=stephen@networkplumber.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).