From: Luca Boccassi <bluca@debian.org>
To: Gavin Hu <gavin.hu@arm.com>, stable@dpdk.org
Cc: nd@arm.com, thomas@monjalon.net, nipun.gupta@nxp.com,
konstantin.ananyev@intel.com
Subject: Re: [dpdk-stable] [PATCH] ring: enforce reading tail before slots
Date: Thu, 24 Oct 2019 09:36:05 +0100 [thread overview]
Message-ID: <897568e675f5d9b5e2ccda64a7c08d88f6f914e1.camel@debian.org> (raw)
In-Reply-To: <1570516723-10217-1-git-send-email-gavin.hu@arm.com>
On Tue, 2019-10-08 at 14:38 +0800, Gavin Hu wrote:
> In weak memory models, like arm64, reading the prod.tail may get
> reordered after reading the ring slots, which corrupts the ring and
> stale data is observed.
>
> This issue was reported by NXP on 8-A72 DPAA2 board. The problem is
> most
> likely caused by missing the acquire semantics when reading
> prod.tail (in SC dequeue) which makes it possible to read a
> stale value from the ring slots.
>
> For MP (and MC) case, rte_atomic32_cmpset() already provides the
> required
> ordering. For SP case, the control depependency between if-statement
> (which
> depends on the read of r->cons.tail) and the later stores to the ring
> slots
> make RMB unnecessary. About the control dependency, read more at:
> https://www.cl.cam.ac.uk/~pes20/ppc-supplemental/test7.pdf
>
>
> This patch is adding the required read barrier to prevent reading the
> ring
> slots get reordered before reading prod.tail for SC case.
>
> Fixes: 0dfc98c507b1 ("ring: separate out head index manipulation")
> Cc:
> stable@dpdk.org
>
>
> Signed-off-by: Gavin Hu <
> gavin.hu@arm.com
> >
> Reviewed-by: Ola Liljedahl <
> ola.liljedahl@arm.com
> >
> Tested-by: Nipun Gupta <
> nipun.gupta@nxp.com
> >
> Acked-by: Nipun Gupta <
> nipun.gupta@nxp.com
> >
> Acked-by: Konstantin Ananyev <
> konstantin.ananyev@intel.com
> >
> ---
> lib/librte_ring/rte_ring.h | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/lib/librte_ring/rte_ring.h b/lib/librte_ring/rte_ring.h
> index e924438..9e6ccfe 100644
> --- a/lib/librte_ring/rte_ring.h
> +++ b/lib/librte_ring/rte_ring.h
> @@ -544,11 +544,14 @@ __rte_ring_move_cons_head(struct rte_ring *r,
> int is_sc,
> return 0;
>
> *new_head = *old_head + n;
> - if (is_sc)
> - r->cons.head = *new_head, success = 1;
> - else
> + if (is_sc) {
> + r->cons.head = *new_head;
> + rte_smp_rmb();
> + success = 1;
> + } else {
> success = rte_atomic32_cmpset(&r->cons.head,
> *old_head,
> *new_head);
> + }
> } while (unlikely(success == 0));
> return n;
> }
>
Acked-by: Luca Boccassi <bluca@debian.org>
Thanks, applied
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2019-10-24 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 6:38 Gavin Hu
2019-10-24 8:36 ` Luca Boccassi [this message]
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=897568e675f5d9b5e2ccda64a7c08d88f6f914e1.camel@debian.org \
--to=bluca@debian.org \
--cc=gavin.hu@arm.com \
--cc=konstantin.ananyev@intel.com \
--cc=nd@arm.com \
--cc=nipun.gupta@nxp.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).