From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id DF80045BC6;
	Thu, 24 Oct 2024 18:34:32 +0200 (CEST)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id CF8A0434FE;
	Thu, 24 Oct 2024 18:34:32 +0200 (CEST)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [45.249.212.189])
 by mails.dpdk.org (Postfix) with ESMTP id F30CE4025C
 for <dev@dpdk.org>; Thu, 24 Oct 2024 18:34:30 +0200 (CEST)
Received: from mail.maildlp.com (unknown [172.19.163.174])
 by szxga03-in.huawei.com (SkyGuard) with ESMTP id 4XZBLR65XVzQs9Y;
 Fri, 25 Oct 2024 00:33:35 +0800 (CST)
Received: from dggpeml100022.china.huawei.com (unknown [7.185.36.176])
 by mail.maildlp.com (Postfix) with ESMTPS id 2F62C140393;
 Fri, 25 Oct 2024 00:34:29 +0800 (CST)
Received: from frapeml500007.china.huawei.com (7.182.85.172) by
 dggpeml100022.china.huawei.com (7.185.36.176) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 15.1.2507.39; Fri, 25 Oct 2024 00:34:28 +0800
Received: from frapeml500007.china.huawei.com ([7.182.85.172]) by
 frapeml500007.china.huawei.com ([7.182.85.172]) with mapi id 15.01.2507.039;
 Thu, 24 Oct 2024 18:34:26 +0200
From: Konstantin Ananyev <konstantin.ananyev@huawei.com>
To: "lihuisong (C)" <lihuisong@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
CC: "mb@smartsharesystems.com" <mb@smartsharesystems.com>,
 "thomas@monjalon.net" <thomas@monjalon.net>, "ferruh.yigit@amd.com"
 <ferruh.yigit@amd.com>, "anatoly.burakov@intel.com"
 <anatoly.burakov@intel.com>, "david.hunt@intel.com" <david.hunt@intel.com>,
 "sivaprasad.tummala@amd.com" <sivaprasad.tummala@amd.com>,
 "stephen@networkplumber.org" <stephen@networkplumber.org>,
 "david.marchand@redhat.com" <david.marchand@redhat.com>, Fengchengwen
 <fengchengwen@huawei.com>, liuyonglong <liuyonglong@huawei.com>
Subject: RE: [PATCH v12 2/3] examples/l3fwd-power: fix data overflow when
 parse command line
Thread-Topic: [PATCH v12 2/3] examples/l3fwd-power: fix data overflow when
 parse command line
Thread-Index: AQHbJQLVy3HZEiVgKkSacwgXKQkJoLKWFsig
Date: Thu, 24 Oct 2024 16:34:26 +0000
Message-ID: <97bf46d4bd824b74859f5a63f338a8c7@huawei.com>
References: <20240320105529.5626-1-lihuisong@huawei.com>
 <20241023040916.1426-1-lihuisong@huawei.com>
 <20241023040916.1426-3-lihuisong@huawei.com>
In-Reply-To: <20241023040916.1426-3-lihuisong@huawei.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.195.32.113]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org


> Many variables are 'uint32_t', like, 'pause_duration', 'scale_freq_min'
> and so on. They use parse_int() to parse it from command line.
> But overflow problem occurs when this function return.
>=20
> Fixes: 59f2853c4cae ("examples/l3fwd_power: add configuration options")
> Cc: stable@dpdk.org
>=20
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> ---

Acked-by: Konstantin Ananyev <konstantin.ananyev@huawei.com>

> 2.22.0