From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id BF7D6A2EDB for ; Tue, 1 Oct 2019 09:42:07 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B0F572A6C; Tue, 1 Oct 2019 09:42:07 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 9A60C2A6C for ; Tue, 1 Oct 2019 09:42:06 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 128A221BF9; Tue, 1 Oct 2019 03:42:03 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 01 Oct 2019 03:42:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding:content-type; s=mesmtp; bh=GjtRAFudWW LWlzQtvKd/OYmGzXRjY8A4AxiDWYN7h68=; b=lhWwEkjhJQ5zvNffNzg94o8XI9 vSt7kxizO/p9SH+jJXgkOUbf4xs6GgqiX7ou5W5qJFOfqlE8PdxXKhRweqzVxh0g TjOu2wAy7799zqFmByLkZYrDzq9Oajjd1P++6sKASHHJDX+iyJVJOBc/90DeE9xj d6kfoaxKnaTObwSEw= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=GjtRAF udWWLWlzQtvKd/OYmGzXRjY8A4AxiDWYN7h68=; b=NhgGAwyDH3XdzxbXMsCmWd HEz+Sw8I5Q0KZ1XBscAYby9hCh3KrXuBnBti2TqH/zmZ9SCZXwpCvzOoiAuzRoPt n1yYXiyuJp4uAky63bkicopvfM5NJTgvaUI1+b7XI9VMmITvR8tWpczVJpKKK0e4 aAtnE0+jLDlaJysA5X8jUDBJ7EDHdcXj0f5DcWgoyPGWAppJUaRv7IIS/4/mTAYf bazldVbk05F8jxiIfEonqI+yPlfLnalbP1mRfg1YYAuf9rU5mZ40LDee1gSvP2TM F3m07uGOcKrt6HaPetjQNSGTeQUCHCYVeTLUSvzN+Wz/6JSPB5Xn8gTLUmidu6OQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrgeefgdduvddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgrshcu ofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukfhppe ejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhm rghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 9639E80060; Tue, 1 Oct 2019 03:42:01 -0400 (EDT) From: Thomas Monjalon To: bluca@debian.org, Gavin Hu Cc: stable@dpdk.org, honnappa.nagarahalli@arm.com, Nipun Gupta , Konstantin Ananyev Date: Tue, 01 Oct 2019 09:41:59 +0200 Message-ID: <2613008.bAPQ5MWe9V@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [dpdk-stable] missing ring memory barrier in 17.11 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" 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?