From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 811BD2BD5 for ; Sun, 16 Sep 2018 11:56:46 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 0F47E21D1E; Sun, 16 Sep 2018 05:56:46 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 16 Sep 2018 05:56:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=n2YR/TepdvYa7Jw1W8RzZ35zjS AbdKc1SQ4IZQUQ6Io=; b=AFBf968o/gvkrU1jSl0KlsxM2B6qBKBgtiwJdae1W3 538SP65vFlaIEUZIF46z4dC4EefrESNu84Xfx73nWcmntjozwiWa+GZHex8tPPpz m2jw1EVoCwTM1MRjg8/rmSpcekp+MTvtIE8ZU2U1erIcgFP1mhcP6k5hbHqhfsAU k= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=n2YR/T epdvYa7Jw1W8RzZ35zjSAbdKc1SQ4IZQUQ6Io=; b=MPif2p9z2IyET31agoWqih MW4p6nMlfoKThvZmf4uKDY6pQhhz4YlIGVWE/peYwo1zxjpXLNEFUBqh2nmIgh76 Jzmt7oXSwklzstPVpfmbMDGzQAKKsDBgh0uKkNGgDGUx/pqvatnM18R800ih1tIs 4M/Yc0h7ncClhkmHDmMSphpqTXwmCtzslspIRaQaMSSsRFx7Lbla8GQF4x+12F1k SiLnOUHdO2cblNYx9n5I8wZchkvl4rdVy24yLYWjmCGCjhQlcjc6Wwv2ShX92+82 bLtAFSa4Mt0eP4EAbsD8g4sUgnEyDicSPob57h+sReyoGOKfwRLuCcjG8Jbq6C5g == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (114.149.6.93.rev.sfr.net [93.6.149.114]) by mail.messagingengine.com (Postfix) with ESMTPA id 23B22102D5; Sun, 16 Sep 2018 05:56:45 -0400 (EDT) From: Thomas Monjalon To: Konstantin Ananyev Cc: dev@dpdk.org Date: Sun, 16 Sep 2018 11:56:44 +0200 Message-ID: <1912621.YvyjYky8PI@xps> In-Reply-To: <1535129226-25510-1-git-send-email-konstantin.ananyev@intel.com> References: <1535129226-25510-1-git-send-email-konstantin.ananyev@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] acl: fix invalid results for rule with zero priority 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: Sun, 16 Sep 2018 09:56:46 -0000 24/08/2018 18:47, Konstantin Ananyev: > If user specifies priority=0 for some of ACL rules > that can cause rte_acl_classify to return wrong results. > The reason is that priority zero is used internally for no-match nodes. > See more details at: https://bugs.dpdk.org/show_bug.cgi?id=79. > The simplest way to overcome the issue is just not allow zero > to be a valid priority for the rule. > > Fixes: dc276b5780c2 ("acl: new library") > > Signed-off-by: Konstantin Ananyev Cc: stable@dpdk.org Applied with below title, thanks acl: forbid rule with priority zero