From: "Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
"bluca@debian.org" <bluca@debian.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"Nipun.gupta@nxp.com" <nipun.gupta@nxp.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-stable] missing ring memory barrier in 17.11
Date: Tue, 8 Oct 2019 06:41:00 +0000 [thread overview]
Message-ID: <VI1PR08MB5376A42F537DD52766339BAD8F9A0@VI1PR08MB5376.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <2613008.bAPQ5MWe9V@xps>
Hi Thomas, Luca,
Thanks for reminding and sorry for late response(due to long holiday).
I have ported the patch and already sent to the stable mailing list, please help check and merge, thanks!
Best Regards,
Gavin
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, October 1, 2019 3:42 PM
> To: bluca@debian.org; Gavin Hu (Arm Technology China)
> <Gavin.Hu@arm.com>
> Cc: stable@dpdk.org; Honnappa Nagarahalli
> <Honnappa.Nagarahalli@arm.com>; Nipun.gupta@nxp.com; Konstantin
> Ananyev <konstantin.ananyev@intel.com>
> Subject: missing ring memory barrier in 17.11
>
> 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?
>
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
prev parent reply other threads:[~2019-10-08 6:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 7:41 Thomas Monjalon
2019-10-01 8:48 ` Luca Boccassi
2019-10-01 14:05 ` Honnappa Nagarahalli
2019-10-08 6:41 ` Gavin Hu (Arm Technology China) [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=VI1PR08MB5376A42F537DD52766339BAD8F9A0@VI1PR08MB5376.eurprd08.prod.outlook.com \
--to=gavin.hu@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bluca@debian.org \
--cc=konstantin.ananyev@intel.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).