Soft Patch Panel
 help / color / mirror / Atom feed
Subject: [spp] [Bug 442] disable ASLR is been highly recommended
Date: Mon, 03 Aug 2020 04:45:13 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Vipin Varghese ( changed:

           What    |Removed                     |Added
           Priority|Normal                      |High
           Severity|normal                      |critical

--- Comment #14 from Vipin Varghese ( ---
Hi Hideyuki,

note: the Bugzilla is raised for the current documentation available

as per the documentation

SPP is a DPDK multi-process application and there are a number of limitations .

Address-Space Layout Randomization (ASLR) is a security feature for memory
protection, but may cause a failure of memory mapping while starting
multi-process application as discussed in dpdk-dev .

ASLR can be disabled by assigning kernel.randomize_va_space to 0, or be enabled
by assigning it to 2.


Thanks for your answer.
[VV] I have asked a question, is ASLR to be enabled or disabled.

SPP20.02 only supports using DPDK20.02. This idea is from first release of SPP
and we are not planning to change it without special reasons.
[VV] From this statement your recommendation is to disable the same.

Why have you shared `2. with `Using DPDK20.02 with ASLR enabled, Segmentaion
fault takes place.`, but the recommendation from SPP team is to disable.`

I am changing the priority to high and critical, waiting for the update from
SPP team.

You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2020-08-03  4:45 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
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 [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).