From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 76EA0A0597 for ; Wed, 8 Apr 2020 03:04:27 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4C46B1BFD1; Wed, 8 Apr 2020 03:04:27 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id 35DFB1BFD1 for ; Wed, 8 Apr 2020 03:04:26 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 0619CA059A; Wed, 8 Apr 2020 03:04:26 +0200 (CEST) From: bugzilla@dpdk.org To: spp@dpdk.org Date: Wed, 08 Apr 2020 01:04:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: SPP X-Bugzilla-Component: main X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: oda@valinux.co.jp X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: yasufum.o@gmail.com X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [spp] [Bug 442] disable ASLR is been highly recommended X-BeenThere: spp@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Soft Patch Panel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: spp-bounces@dpdk.org Sender: "spp" https://bugs.dpdk.org/show_bug.cgi?id=3D442 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 proce= sses at the moment. There is a case that a secondary process try to free a mempool that was cre= ated 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, segmentat= ion fault will occur at freeing mempool. --=20 You are receiving this mail because: You are on the CC list for the bug.=