Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp3867225ybg; Sun, 7 Jun 2020 13:11:34 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzHAwt94LItBVzRkwftuvZ2OzeMtExDt54ZfCj/zvzxc3UX9nxjgjNbwkd6ZPTs6FeU4TEZ X-Received: by 2002:a50:9b0f:: with SMTP id o15mr19674600edi.325.1591560693762; Sun, 07 Jun 2020 13:11:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591560693; cv=none; d=google.com; s=arc-20160816; b=D9fOrfmjjAtXAgC4TFORbB/9X0db+iSnCzAxOeCYMIvwZXYtPF2HhS3+xRGWrEAPMC V9dkYsK93JO1ZcAQGW+mll0v5aJZ9ZMhD3ULLGcDBR7WuMr8QAm4zHEB1TuIJx1FEiON 6G5/IDiV69Yd4dY051HuV9lKgqPyx92r0+7ks5mqWRHs9p9d6Hp24t8glBa1h1GHX7x9 l9Al5VjSwzqTYR3ixT0pEIIKok9sjupaYSV4J3e602lT6pYduQhhOd5XDQ8bSl79Thmt +2jxatpd3sanyQiRqO5RBcpesnPZn6KziNS4D6R6vTkC4dV0GiXLSR2hj8krc3raAqOH YAwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=0noNmQ0fhu60NKeOC7i5j1jRIJXEsizVoqni72PGkUY=; b=OwuqPeL9ZnxO0JR6tJdHqPoioTt84a3rTeH+5iJV2o3Nuwp/MMtrHD4fpWSmieKk3/ RIzicto1H+BazMYIYHUGekCYwz8YCcj6jh5OZkZ3W72Jv34wO6hs8sjgBPRJ1jCSwPHf fQhsVStW06aExUD/e4wuyr63xNcBEhghwpmaeXX64fN4AndFXE111fhc7Y/+C2U9FXMh QKa7NW6ZlK9GsXP5Ifo3KxoICCb8MlmjlR71HEIrrbd/GjB5u7XEi/L+H1ukb2FowN2m VzD9aClkEbN6fGVcvQGI+M0ktf81g+ZqCcNhJZq28LZcv6ndYmDVnZJ1ey3DElaHayXj 1Alw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k91si63400edc.296.2020.06.07.13.11.09; Sun, 07 Jun 2020 13:11:33 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726985AbgFGUJO (ORCPT + 99 others); Sun, 7 Jun 2020 16:09:14 -0400 Received: from jabberwock.ucw.cz ([46.255.230.98]:50840 "EHLO jabberwock.ucw.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726679AbgFGUJN (ORCPT ); Sun, 7 Jun 2020 16:09:13 -0400 Received: by jabberwock.ucw.cz (Postfix, from userid 1017) id 5ADE61C0BD2; Sun, 7 Jun 2020 22:09:11 +0200 (CEST) Date: Sun, 7 Jun 2020 22:09:11 +0200 From: Pavel Machek To: Greg Kroah-Hartman Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org, fengsheng , Xinwei Kong , Mark Brown , Sasha Levin Subject: Re: [PATCH 4.19 15/28] spi: dw: use "smp_mb()" to avoid sending spi data error Message-ID: <20200607200910.GA13138@amd> References: <20200605140252.338635395@linuxfoundation.org> <20200605140253.279609547@linuxfoundation.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline In-Reply-To: <20200605140253.279609547@linuxfoundation.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > Because of out-of-order execution about some CPU architecture, > In this debug stage we find Completing spi interrupt enable -> > prodrucing TXEI interrupt -> running "interrupt_transfer" function > will prior to set "dw->rx and dws->rx_end" data, so this patch add > memory barrier to enable dw->rx and dw->rx_end to be visible and > solve to send SPI data error. So, this is apparently CPU-vs-device issue... > +++ b/drivers/spi/spi-dw.c > @@ -304,6 +304,9 @@ static int dw_spi_transfer_one(struct spi_controller = *master, > dws->len =3D transfer->len; > spin_unlock_irqrestore(&dws->buf_lock, flags); > =20 > + /* Ensure dw->rx and dw->rx_end are visible */ > + smp_mb(); > + But we use SMP-only memory barrier, thus the bug will still be there in single-processor configurations. Should this be mb()? Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAl7dSWYACgkQMOfwapXb+vK1GgCeKhaQnkGotAXJ3JtVtBG/A9mH rU0AniQYz4+EoB5HTc6vo3KNbewgHGFg =8y43 -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY--