From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 34156A034D; Wed, 16 Feb 2022 18:13:07 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D09EF410FF; Wed, 16 Feb 2022 18:13:06 +0100 (CET) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id 725DD40150 for ; Wed, 16 Feb 2022 18:13:05 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id F1D485C0225; Wed, 16 Feb 2022 12:13:02 -0500 (EST) Received: from imap48 ([10.202.2.98]) by compute2.internal (MEProxy); Wed, 16 Feb 2022 12:13:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=u256.net; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; bh=lMDohB3qW83nRJaPh8Oi6mpAcycDsOtMfDmLbx mMVDE=; b=J4o5wz6JoCbf9RMUAqm05i4eg8RxHpg3V2rJO6O9mY5YoZCJVX/6y2 K8Drjf/BSowETMgKewuSyPQI/Y0Z1TjqDZrIJ+32jmrJpRWQ9zoehmP4ej5oYuoM jH7ZPpsndpSNrIwpnDr1bcM4w85DSfAJprXZZr2KhAUCgPR9m31oyciPl7wXGuZx sAUlDQ++IAyHO6pPBnOgYf6z4lzzWNDFDlCN67sbgDCwLweR4dTM/YNOlr83umx4 l18ElOAFODVQ+5gXgcyETMWKSP9MGlab5WsvicOi+E+gm+LTLd+msK90OoYND7QG BwkeKMZPiN5XmSkpD2ulZBhwlOw+kvGg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=lMDohB3qW83nRJaPh 8Oi6mpAcycDsOtMfDmLbxmMVDE=; b=mEYmifJ5C+iyH06T9G26aWbNNz+7v8F4Q cLf/Tg14uRq/nX22t7DtdprSwjfWJWdx1m8vPzaHZjyqT5RFRqMGgvJE0Ylg8Sx2 2JG5MPFoHWvncmNmUXHI/cmUGYVJGHv/5dqVJIYp+nwfkLg6vZ2jzcbbxPXcGgk8 bvqKU3sjh3YOC9dPsDOsddqNE48L78E/U5YxbXu6H0jcqf87bqYmxm+mCWsIrdhr XNz67yD02+oXc05G7Kuuk90sG+ReQtD9eMZ5rfiw004FACY2c3HtJCg0N1jYKexX CS0WVTgDXeMfFtqfpuiRkZokifDD+xjm2q7pnsicngIciBFtesEfg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrjeeigdeljecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtsehttdertderreejnecuhfhrohhmpefirgotthgr nhgptfhivhgvthcuoehgrhhivhgvsehuvdehiedrnhgvtheqnecuggftrfgrthhtvghrnh epgfeuhfffleeludeuheeuteeufeegtdeiveduudfhgeevteeutdelueffueehkeefnecu vehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrihhvvg esuhdvheeirdhnvght X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id F111821E0026; Wed, 16 Feb 2022 12:13:01 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-4776-gd3673c9443-fm-20220215.001-gd3673c94 Mime-Version: 1.0 Message-Id: <056a903d-ae14-419c-85d4-f512dc239d9b@www.fastmail.com> In-Reply-To: References: <20220210071052.527-1-madhuker.mythri@oracle.com> <20220210170131.2199922-1-grive@u256.net> Date: Wed, 16 Feb 2022 18:12:40 +0100 From: =?UTF-8?Q?Ga=C3=ABtan_Rivet?= To: "David Marchand" Cc: dev , "madhuker.mythri" , "Ferruh Yigit" Subject: Re: [PATCH] devargs: Fix rte_devargs_parse uninitialized calls Content-Type: text/plain X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Tue, Feb 15, 2022, at 16:27, David Marchand wrote: > On Thu, Feb 10, 2022 at 6:01 PM Gaetan Rivet wrote: >> >> The function rte_devargs_parse() previously was safe to call with >> non-initialized devargs structure as parameter. >> >> When adding the support for the global device syntax, >> this assumption was broken. Restore it by forcing memset as part of >> the call itself. >> >> Bugzilla Id: 933 > > Nit: Bugzilla ID* > >> Fixes: b344eb5d941a ("devargs: parse global device syntax") > > We need a backport in 21.11, right? Hi David, yes it should be in 21.11 as well. -- Gaetan Rivet