From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dumitrescu, Cristian" Subject: Re: [PATCH v5 2/6] librte_table: fix acl lookup function Date: Wed, 20 Sep 2017 12:24:20 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BABCEB2@IRSMSX108.ger.corp.intel.com> References: <1504693668-2062-1-git-send-email-bernard.iremonger@intel.com> <1504802598-27296-3-git-send-email-bernard.iremonger@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "stable@dpdk.org" To: "Iremonger, Bernard" , "dev@dpdk.org" , "Yigit, Ferruh" , "Ananyev, Konstantin" , "adrien.mazarguil@6wind.com" Return-path: In-Reply-To: <1504802598-27296-3-git-send-email-bernard.iremonger@intel.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > -----Original Message----- > From: Iremonger, Bernard > Sent: Thursday, September 7, 2017 5:43 PM > To: dev@dpdk.org; Yigit, Ferruh ; Ananyev, > Konstantin ; Dumitrescu, Cristian > ; adrien.mazarguil@6wind.com > Cc: Iremonger, Bernard ; stable@dpdk.org > Subject: [PATCH v5 2/6] librte_table: fix acl lookup function >=20 > The rte_table_acl_lookup() function was returning data from acl_memory > instead of acl_rule_memory. >=20 > Fixes: 166923eb2f78 ("table: ACL") > Cc: stable@dpdk.org >=20 > Signed-off-by: Bernard Iremonger > --- > lib/librte_table/rte_table_acl.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) >=20 > diff --git a/lib/librte_table/rte_table_acl.c b/lib/librte_table/rte_tabl= e_acl.c > index e84b437..258916d 100644 > --- a/lib/librte_table/rte_table_acl.c > +++ b/lib/librte_table/rte_table_acl.c > @@ -794,7 +794,7 @@ struct rte_table_acl { > if (action_table_pos !=3D 0) { > pkts_out_mask |=3D pkt_mask; > entries[pkt_pos] =3D (void *) > - &acl->memory[action_table_pos * > + &acl->acl_rule_memory[action_table_pos * > acl->entry_size]; > rte_prefetch0(entries[pkt_pos]); > } > -- > 1.9.1 NACK Existing code is correct, proposed code changes are wrong (for same reasons= described in patch 1 of this patch set).