From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH v6] eal: fix core number validation Date: Thu, 17 Jan 2019 12:19:16 +0000 Message-ID: <20190117121916.GA319108@bricha3-MOBL.ger.corp.intel.com> References: <1547216106-13680-1-git-send-email-hari.kumarx.vemula@intel.com> <1547727192-25126-1-git-send-email-hari.kumarx.vemula@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, david.marchand@redhat.com, reshma.pattan@intel.com, ferruh.yigit@intel.com, jananeex.m.parthasarathy@intel.com, stable@dpdk.org To: Hari Kumar Vemula Return-path: Content-Disposition: inline In-Reply-To: <1547727192-25126-1-git-send-email-hari.kumarx.vemula@intel.com> 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 Thu, Jan 17, 2019 at 12:13:12PM +0000, Hari Kumar Vemula wrote: > When incorrect core value or range provided, > as part of -l command line option, a crash occurs. > > Added valid range checks to fix the crash. > > Added ut check for negative core values. > Added unit test case for invalid core number range. > > Fixes: d888cb8b9613 ("eal: add core list input format") > Cc: stable@dpdk.org > > Signed-off-by: Hari Kumar Vemula > Reviewed-by: David Marchand > -- > v6: Changed testcase order > v5: Corrected unit test case for -l option > v4: Used RTE_MAX_LCORE for max core check > v3: Added unit test cases for invalid core number range > v2: Replace strtoul with strtol > Modified log message > --- > lib/librte_eal/common/eal_common_options.c | 9 +++- > test/test/test_eal_flags.c | 61 ++++++++++++++-------- > 2 files changed, 45 insertions(+), 25 deletions(-) > Is this patch related to, or does it fix Bugzilla #19? https://bugs.dpdk.org/show_bug.cgi?id=19 /Bruce