From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Rybchenko Subject: Re: [PATCH 1/4] net/failsafe: avoid rte_memcpy if rte_realloc fails Date: Thu, 8 Nov 2018 09:20:13 +0300 Message-ID: <5e6dc720-b16c-6ce1-e024-aef7f1bd447a@solarflare.com> References: <20181106193005.5383-1-stephen@networkplumber.org> <20181106193005.5383-2-stephen@networkplumber.org> <5d2c4750-b418-c4fe-4e20-d7cc7ca4efe7@solarflare.com> <20181107101502.2cbaffde@shemminger-XPS-13-9360> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Cc: To: Stephen Hemminger Return-path: Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) by dpdk.org (Postfix) with ESMTP id 8DE31239 for ; Thu, 8 Nov 2018 07:20:22 +0100 (CET) In-Reply-To: <20181107101502.2cbaffde@shemminger-XPS-13-9360> Content-Language: en-GB List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 11/7/18 9:15 PM, Stephen Hemminger wrote: > Any solution is fine because of that. You could flag it as false in Coverity > or change code to avoid warning. Just want to get it fixed, don't care how. Done, marked it as false positive in Coverity and provided explanation why. Andrew.