DPDK patches and discussions
 help / color / mirror / Atom feed
From: 张伟 <zhangwqh@126.com>
To: dev@dpdk.org
Cc: "Zhu, Heqing" <heqing.zhu@intel.com>,
	Dmitrii.Kuvaiskii@tu-dresden.de,
	 oleksii.oleksenko@tu-dresden.de, enkovich.gnu@gmail.com
Subject: [dpdk-dev] rte_eth_rx_burst reports bug by safecode (one memory protection tool)
Date: Tue, 20 Sep 2016 02:36:36 +0800 (CST)	[thread overview]
Message-ID: <7316bd44.1db.15743bc4bf3.Coremail.zhangwqh@126.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GBK, Size: 971 bytes --]

Hi all, 


I am using a memory safe tool safecode   http://safecode.cs.illinois.edu/    compiling dpdk application. If I do not do the memory safety checking, it works correctly.  But my main aim is to evaluate if using safecode protects the memory, what's the overhead? 

The related compiling option is 

CFLAGS += -O3 -fmemsafety

CC=clang

If I enabled -O3  -fmemsafety, dpdk lib interface rte_eth_rx_burst trigger the following bug:  

https://gist.github.com/zhangwei1984/ee8ddf6868d6be9b6bc6f35c3cdeb850

Does it really have bug?  I do not have enough ability to detect where it might bring this problem. Can anyone help to see this problem who focuses on this area development? I will be very appreciated. 

Thanks, 

wei





\x16º&¥¦å¡×¥j¶ ¹ªÜ†)ízW(˜Ê'Iêu÷m7ëvÓ^‘zÛ«œö­†–›–‡^•ªÚ‚æ«r\x18§µé\¢d^qè¯y×ë¢i kMbž×¥r‰¦­5Š{^•Ê&×ݹ睼ñ¼¥Ù(®\x03è²×âÇ\b­„DŒLøï~\x04ó~Ááú+uëÝ¥Ù(®\x03(Ÿ_Rz´×­´ß®uûM´Ð!\x12M\x17œz+Þuú蚊ìš\x06´ÓXߊ{^•Ê&×NöÓÝ|o'æ²h\x1a×M_š)ízW(›\b­„DŒLý}IêvÓ^µ×~¹ÓNôÑq1´º(§]W"º'>Ší\x01Q

                 reply	other threads:[~2016-09-19 18:36 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=7316bd44.1db.15743bc4bf3.Coremail.zhangwqh@126.com \
    --to=zhangwqh@126.com \
    --cc=Dmitrii.Kuvaiskii@tu-dresden.de \
    --cc=dev@dpdk.org \
    --cc=enkovich.gnu@gmail.com \
    --cc=heqing.zhu@intel.com \
    --cc=oleksii.oleksenko@tu-dresden.de \
    /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).