[dpdk-stable] missing ring memory barrier in 17.11

[Honnappa Nagarahalli]

China team is on holiday. Yes, we should apply this patch to 17.11

> -----Original Message-----
> From: Luca Boccassi <bluca at debian.org>
> Sent: Tuesday, October 1, 2019 3:48 AM
> To: thomas at monjalon.net; Gavin Hu (Arm Technology China)
> <Gavin.Hu at arm.com>
> Cc: stable at dpdk.org; Honnappa Nagarahalli
> <Honnappa.Nagarahalli at arm.com>; Nipun.gupta at nxp.com; Konstantin
> Ananyev <konstantin.ananyev at intel.com>
> Subject: Re: missing ring memory barrier in 17.11
> 
> On Tue, 2019-10-01 at 09:41 +0200, Thomas Monjalon wrote:
> > Hi Luca, Gavin,
> >
> > It seems the fix 85cffb2eccd9 ("ring: enforce reading tail before
> > slots")
> > should be backported in 17.11.
> >
> > This patch is missing because the root cause is wrongly identified.
> > It is referenced as
> > 	Fixes: c9fb3c62896f ("ring: move code in a new header file") in
> > 18.02, but in reality it is from 17.05:
> > 	Fixes: 0dfc98c507b1 ("ring: separate out head index
> > manipulation")
> >
> > Do you agree?
> 
> Hi,
> 
> Makes sense to me, and it applies cleanly (after accounting for the source file
> name change). I'll queue it up for 17.11.8.
> 
> --
> Kind regards,
> Luca Boccassi