From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v5] eal: out-of-bounds write Date: Mon, 20 Jun 2016 12:09:55 +0200 Message-ID: <5727542.OiCZAjWWDW@xps13> References: <1466088738-16990-1-git-send-email-slawomirx.mrozowicz@intel.com> <3354397.Tgjzuq1405@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Slawomir Mrozowicz , dev@dpdk.org, david.marchand@6wind.com To: Sergio Gonzalez Monroy Return-path: Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by dpdk.org (Postfix) with ESMTP id D59DD8E74 for ; Mon, 20 Jun 2016 12:10:02 +0200 (CEST) Received: by mail-wm0-f53.google.com with SMTP id r201so54298058wme.1 for ; Mon, 20 Jun 2016 03:10:02 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-06-20 10:38, Sergio Gonzalez Monroy: > On 20/06/2016 10:14, Thomas Monjalon wrote: > >> + RTE_LOG(ERR, EAL, > >> + "All memory segments exhausted by IVSHMEM. " > > There is no evidence that it is related to IVSHMEM. > > "Not enough memory segments." would be more appropriate. > > Actually we would hit this issue when all memsegs have been used by IVSHMEM. > So I think the message is accurate. I think it's saner to avoid mixing "potential root cause of a use case" and "accurate description of the error". One day, the root cause could be different and the message will become wrong. Here there is not enough memory segment.