From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Konstantin Ananyev" <konstantin.ananyev@intel.com>,
"Stephen Hemminger" <stephen@networkplumber.org>
Cc: "dpdk-dev" <dev@dpdk.org>, "Jerin Jacob" <jerinj@marvell.com>
Subject: [dpdk-dev] packet data access bug in bpf and pdump libs
Date: Wed, 9 Oct 2019 13:03:41 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35C60B67@smartserver.smartshare.dk> (raw)
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.
Med venlig hilsen / kind regards
- Morten Brørup
next reply other threads:[~2019-10-09 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 11:03 Morten Brørup [this message]
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
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=98CBD80474FA8B44BF855DF32C47DC35C60B67@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).