Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp2464278imj; Mon, 18 Feb 2019 06:29:40 -0800 (PST) X-Google-Smtp-Source: AHgI3IZq2iiPfip7EB2v6RciYd+PIgQ/Tqe1AyVQiKzvJ+LUOw+rKPTe0EnrcidliYTYpw7JZRRn X-Received: by 2002:a63:d052:: with SMTP id s18mr18847550pgi.11.1550500180588; Mon, 18 Feb 2019 06:29:40 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550500180; cv=none; d=google.com; s=arc-20160816; b=eDjlvPCRWHjxK3L2XLV/05UaUe8TZAPzFctg/ISIBXErfhqEZiTyt4XCcZIVjf95XI 9VCsnZ/YO/opPVsVeFRcJYu3/s/fuVqpfkFKfVLTwH2BoUO/LYXHwnmpWlRr0EUdxg/g XTeV032k5nJMP4YnKWWbN/FKPY86DVFBhtiWCy2P4uhqDaREMQdAOCuzJEJ2amEkFaMQ iiffv8IgwqQovjK5tu/QBDPuKKzGNNjlbg1PsUZVbKiFel0lInuPctYR94VasSSqFvyQ MZhXIdDW0cHw6r0TQlU/SVmaZUuIdhRfaURIdOhoJ2xqlCdnAZxhXt0CJx3HFZYkWFWU RQCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=725JFSPSwecr0cXar9aAC+16zItBSVQA/WE0KB3dvco=; b=dsNVsN5nnAmxEZ5XuTTW1LG6EgRr88sJy7YxAAQPzjlerI6yweJGK4hUHxVjMT1rZm BQiuArqIMEYwVik05IqElyioV3K65VxulEKD53eD3I8IXkS7DvG9nNQbCIkRFk6HZ5lq LyPbvsPZAbApLBA7K6zJDPWkFgG1K+VELrEVtVKaJpEz/bbI+yhzKlF6PCYBxd2V/2tY LwTy53XHNJEwt9N3ZeEG4XsziOeNAh6hlXpnnIpOTY+Fzlp1jFH3rmr85iI6t7xqIP4P erujdqCdtR5/XNJF8cmt/6V9CqctlSWaUTMmnA37ceOwpYFmk6yMI7nvwGErDvs04HCk WsMQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=L6870o02; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g17si12570024pgi.578.2019.02.18.06.29.24; Mon, 18 Feb 2019 06:29:40 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=L6870o02; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389155AbfBROBq (ORCPT + 99 others); Mon, 18 Feb 2019 09:01:46 -0500 Received: from mail.kernel.org ([198.145.29.99]:43262 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389146AbfBROBn (ORCPT ); Mon, 18 Feb 2019 09:01:43 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B1C7721905; Mon, 18 Feb 2019 14:01:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550498503; bh=WFgEMJyWIWxaeDBTbHRgzgSTwQtI/vpgNHMunlbNpIA=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=L6870o02QPOHzS59NgTdHJHoekdOtl/ikPVHC6oSwMpuQwYUkhk2gmabDg4bl5GNZ Y67sK7VrikQ3X2Dq0CrInO5X4pdzhjercCFXiOrpCc6kxZPZcjILpsEAqAQc5BN57D nWwmabrViesL39BREO8gYsrOhfHFmS76v/G+n6DY= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Robin Murphy , Will Deacon , Sasha Levin Subject: [PATCH 4.4 030/143] iommu/arm-smmu-v3: Use explicit mb() when moving cons pointer Date: Mon, 18 Feb 2019 14:42:38 +0100 Message-Id: <20190218133530.244329883@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190218133529.099444112@linuxfoundation.org> References: <20190218133529.099444112@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.4-stable review patch. If anyone has any objections, please let me know. ------------------ [ Upstream commit a868e8530441286342f90c1fd9c5f24de3aa2880 ] After removing an entry from a queue (e.g. reading an event in arm_smmu_evtq_thread()) it is necessary to advance the MMIO consumer pointer to free the queue slot back to the SMMU. A memory barrier is required here so that all reads targetting the queue entry have completed before the consumer pointer is updated. The implementation of queue_inc_cons() relies on a writel() to complete the previous reads, but this is incorrect because writel() is only guaranteed to complete prior writes. This patch replaces the call to writel() with an mb(); writel_relaxed() sequence, which gives us the read->write ordering which we require. Cc: Robin Murphy Signed-off-by: Will Deacon Signed-off-by: Sasha Levin --- drivers/iommu/arm-smmu-v3.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/drivers/iommu/arm-smmu-v3.c b/drivers/iommu/arm-smmu-v3.c index fc6eb752ab35..eb9937225d64 100644 --- a/drivers/iommu/arm-smmu-v3.c +++ b/drivers/iommu/arm-smmu-v3.c @@ -683,7 +683,13 @@ static void queue_inc_cons(struct arm_smmu_queue *q) u32 cons = (Q_WRP(q, q->cons) | Q_IDX(q, q->cons)) + 1; q->cons = Q_OVF(q, q->cons) | Q_WRP(q, cons) | Q_IDX(q, cons); - writel(q->cons, q->cons_reg); + + /* + * Ensure that all CPU accesses (reads and writes) to the queue + * are complete before we update the cons pointer. + */ + mb(); + writel_relaxed(q->cons, q->cons_reg); } static int queue_sync_prod(struct arm_smmu_queue *q) -- 2.19.1