From: =?gb18030?B?zfXJz+S/?= <438515698@qq.com>
To: =?gb18030?B?ZGV2?= <dev@dpdk.org>
Subject: [dpdk-dev] double free mbuf causing Data Coverage Problem
Date: Tue, 22 Jun 2021 22:57:40 +0800 [thread overview]
Message-ID: <tencent_21169FAF985B0D505C168F4E487864B8DC06@qq.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 382 bytes --]
At dpdk19.08, I executed twice for the same mbuf by rte_pktmbuf_free_seg(), which stores two identical pointers in the cache, causes the device to be overwritten when I apply for mbuf consecutively, because rte_pktbuf_free_seg guarantees refcnt==1 after the mbuf is released. Why do you want to do this? This is not the problem at 17.02,when the refcnt is 0 after mbuf released
reply other threads:[~2021-06-28 7:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tencent_21169FAF985B0D505C168F4E487864B8DC06@qq.com \
--to=438515698@qq.com \
--cc=dev@dpdk.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).