From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier MATZ Subject: Re: Random mbuf corruption Date: Tue, 24 Jun 2014 13:01:55 +0200 Message-ID: <53A95AA3.90408@6wind.com> References: <53A43E5E.3030809@windriver.com> <20140624104859.GA19229@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Neil Horman , Stefan Baranoff Return-path: In-Reply-To: <20140624104859.GA19229-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" Hi, On 06/24/2014 12:48 PM, Neil Horman wrote: > Sounds like it might be time to add in some poisoning options to the mbuf > allocator. Such option already exists: CONFIG_RTE_LIBRTE_MBUF_DEBUG and RTE_LIBRTE_MEMPOOL_DEBUG will enable some runtime checks, at least double free and buffer overflows. Olivier