patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: bluca@debian.org, Gavin Hu <gavin.hu@arm.com>
Cc: stable@dpdk.org, honnappa.nagarahalli@arm.com,
	Nipun Gupta <nipun.gupta@nxp.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-stable] missing ring memory barrier in 17.11
Date: Tue, 01 Oct 2019 09:41:59 +0200	[thread overview]
Message-ID: <2613008.bAPQ5MWe9V@xps> (raw)

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?



             reply	other threads:[~2019-10-01  7:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01  7:41 Thomas Monjalon [this message]
2019-10-01  8:48 ` Luca Boccassi
2019-10-01 14:05   ` Honnappa Nagarahalli
2019-10-08  6:41 ` Gavin Hu (Arm Technology China)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2613008.bAPQ5MWe9V@xps \
    --to=thomas@monjalon.net \
    --cc=bluca@debian.org \
    --cc=gavin.hu@arm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=nipun.gupta@nxp.com \
    --cc=stable@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).