Soft Patch Panel
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: spp@dpdk.org
Subject: [spp] [Bug 442] disable ASLR is been highly recommended
Date: Wed, 08 Apr 2020 01:04:26 +0000	[thread overview]
Message-ID: <bug-442-394-Th9KLnsfAo@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-442-394@http.bugs.dpdk.org/>

https://bugs.dpdk.org/show_bug.cgi?id=442

Itsuro Oda (oda@valinux.co.jp) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |oda@valinux.co.jp

--- Comment #1 from Itsuro Oda (oda@valinux.co.jp) ---
It is a work around that is necessary to use vhost PMD from secondary processes
at the moment.
There is a case that a secondary process try to free a mempool that was created
by another secondary process (although it is not intentional). The free
function address that is registered at the creation is used to free mempool. If
the free function address is different among secondary processes, segmentation
fault will occur at freeing mempool.

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

  reply	other threads:[~2020-04-08  1:04 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 [this message]
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

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-Th9KLnsfAo@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).