From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.warmcat.com (mail.warmcat.com [163.172.24.82]) by dpdk.org (Postfix) with ESMTP id B51BC1C6B4; Fri, 11 May 2018 15:39:19 +0200 (CEST) To: "De Lara Guarch, Pablo" , "dev@dpdk.org" Cc: "stable@dpdk.org" , "Mody, Rasesh" , "Patil, Harish" , "Shahed.Shaikh@cavium.com" References: <152600304856.53146.9681482138854493833.stgit@localhost.localdomain> <152600316103.53146.10955338688055072616.stgit@localhost.localdomain> <1a5248e0-d33f-db7c-748e-39805a111aa2@warmcat.com> From: Andy Green Message-ID: <7462e3b8-d0ec-a90f-0fa8-bae565ce6634@warmcat.com> Date: Fri, 11 May 2018 21:38:41 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v4 09/18] net/qede: strncpy length constant and NUL X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2018 13:39:19 -0000 On 05/11/2018 08:48 PM, De Lara Guarch, Pablo wrote: > > >> -----Original Message----- >> From: Andy Green [mailto:andy@warmcat.com] >> Sent: Friday, May 11, 2018 11:48 AM >> To: De Lara Guarch, Pablo ; dev@dpdk.org >> Cc: stable@dpdk.org; Mody, Rasesh ; Patil, Harish >> ; Shahed.Shaikh@cavium.com >> Subject: Re: [dpdk-dev] [PATCH v4 09/18] net/qede: strncpy length constant and >> NUL >> >> >> >> On 05/11/2018 06:43 PM, De Lara Guarch, Pablo wrote: >>> >>> >>>> -----Original Message----- >>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Andy Green >>>> Sent: Friday, May 11, 2018 2:46 AM >>>> To: dev@dpdk.org >>>> Subject: [dpdk-dev] [PATCH v4 09/18] net/qede: strncpy length >>>> constant and NUL >>>> >>>> Signed-off-by: Andy Green >>>> --- >>>> drivers/net/qede/base/ecore_int.c | 8 +++++--- >>>> 1 file changed, 5 insertions(+), 3 deletions(-) >>>> >>>> diff --git a/drivers/net/qede/base/ecore_int.c >>>> b/drivers/net/qede/base/ecore_int.c >>>> index f43781ba4..d9e22b5ed 100644 >>>> --- a/drivers/net/qede/base/ecore_int.c >>>> +++ b/drivers/net/qede/base/ecore_int.c >>>> @@ -6,6 +6,8 @@ >>>> * See LICENSE.qede_pmd for copyright and licensing details. >>>> */ >>>> >>>> +#include >>>> + >>>> #include "bcm_osal.h" >>>> #include "ecore.h" >>>> #include "ecore_spq.h" >>>> @@ -1104,9 +1106,9 @@ static enum _ecore_status_t >>>> ecore_int_deassertion(struct ecore_hwfn *p_hwfn, >>>> p_aeu->bit_name, >>>> num); >>>> else >>>> - OSAL_STRNCPY(bit_name, >>>> - p_aeu->bit_name, >>>> - 30); >>>> + strlcpy(bit_name, >>>> + p_aeu->bit_name, >>>> + sizeof(bit_name)); >>>> >>>> /* We now need to pass bitmask in its >>>> * correct position. >>> >>> I'd say it should be better to change OSAL_STRNCPY to OSAL_STRLCPY and >>> modify the macro to use strlcpy, so we avoid further uses of that strlcpy. >>> >>> However, this modifies base driver code, so it is up to the maintainers to make >> that decision. >>> (CC'ing maintainers here). >> >> There's no value for any OSAL_* that simply defines itself to be the same as the >> direct api, as does OSAL_STRNCPY. >> >> It's better to just remove any OSAL_* that calls straight through since all it does >> is obfuscate what the code does, for no benefit. > > I agree. Since this is modifying base driver code, > the maintainers can decide what to do with this. > >> >>> Also, missing fixes line and CC stable. >>> >>> Fixes: 8427c6647964 ("net/qede/base: add attention formatting string") >> >> The idea of this "Fixes" thing is to look up in git blame what is being edited is it? >> If so what's the benefit of that over using git if you ever want to know that? >> > > This is important mainly to see which releases needed this patch backported. > I am replying to your patches with this info, to save you some time > (I know you are feeling the pain of this overhead :P). Yeah: I appreciate the help. Some of the current rules make assumptions about burning time for no real benefit that assume the contributor has no choice but to comply. But that is simply not true for all potential contributors. I will integrate the comments tomorrow morning (ie, +12h) and push again. I will look closer at the missing include thing, but since build stops, telling me it can't find the include file, and the patch fixes it, there are a limited amount of possible root causes. -Andy > >> -Andy >> >>> Cc: stable@dpdk.org >>>