* [dpdk-dev] double free mbuf causing Data Coverage Problem
@ 2021-06-22 14:57 =?gb18030?B?zfXJz+S/?=
0 siblings, 0 replies; only message in thread
From: =?gb18030?B?zfXJz+S/?= @ 2021-06-22 14:57 UTC (permalink / raw)
To: =?gb18030?B?ZGV2?=
[-- 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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-06-28 7:15 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-22 14:57 [dpdk-dev] double free mbuf causing Data Coverage Problem =?gb18030?B?zfXJz+S/?=
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).