From: bugzilla@dpdk.org
To: spp@dpdk.org
Subject: [spp] [Bug 442] disable ASLR is been highly recommended
Date: Mon, 13 Jul 2020 02:31:26 +0000 [thread overview]
Message-ID: <bug-442-394-3drpaGvw4v@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-442-394@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=442
masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |masahiro.nemoto.es@s1.ntt-t
| |x.co.jp
--- Comment #4 from masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) ---
Hello Vipin,
Apologize about my late reply.
First of all, we have tried '--base-virtaddr and --single-file-segments' option
when starting primary process using DPDK20.02, ASLR enabled.
1. Result with DPDK20.02
Segmentation fault was observed when two secondary process(spp_vf) try to use
vhost.
2. Result with DPDK20.05
Segmentaion fault was NOT observed with the same condition above.
3. Analysis
Vhost related bug is fixed and merged from DPDK20.05 and this maybe the cause
difference of results.
(commit 7470f845c17ac27ce08b22f3c024169e51ade990)
4. Document impact
- Document for SPP 20.02, ASLR disable can NOT be deleted.
- Document for SPP 20.05 or onward, ASLR disable can be deleted(but should be
tested carefully)
What do you think?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-07-13 2:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 6:19 bugzilla
2020-04-08 1:04 ` bugzilla
2020-04-08 2:37 ` bugzilla
2020-04-08 2:40 ` bugzilla
2020-07-13 2:31 ` bugzilla [this message]
2020-07-20 1:28 ` bugzilla
2020-07-28 3:59 ` bugzilla
2020-07-29 0:52 ` bugzilla
2020-07-30 2:39 ` bugzilla
2020-07-30 2:40 ` bugzilla
2020-07-30 2:41 ` bugzilla
2020-07-30 2:42 ` bugzilla
2020-07-30 6:05 ` bugzilla
2020-08-03 1:46 ` bugzilla
2020-08-03 4:45 ` bugzilla
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=bug-442-394-3drpaGvw4v@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=spp@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).