linux-kernel - Re: [PATCH] spi: dw: use "smp_mb()" to avoid sending spi data error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 27 Dec 2019 00:22:40 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Xinwei Kong <kong.kongxinwei@...ilicon.com>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        linuxarm@...wei.com, fengsheng <fengsheng5@...wei.com>
Subject: Re: [PATCH] spi: dw: use "smp_mb()" to avoid sending spi data error

On Thu, Dec 26, 2019 at 05:21:28PM +0800, Xinwei Kong wrote:
> this patch will add memory barrier to ensure this "struct dw_spi *dws"
> to complete data setting before enabling this SPI hardware interrupt.
> eg:
> it will fix to this following low possibility error in testing environment
> which using SPI control to connect TPM Modules

> --- a/drivers/spi/spi-dw.c
> +++ b/drivers/spi/spi-dw.c
> @@ -288,6 +288,8 @@ static int dw_spi_transfer_one(struct spi_controller *master,
>  	dws->rx_end = dws->rx + transfer->len;
>  	dws->len = transfer->len;
>  
> +	smp_mb();
> +
>  	spi_enable_chip(dws, 0);

I'd be much more comfortable here if I understood what this was
supposed to be syncing - what exactly gets flushed here and why
is a memory barrier enough to ensure it's synced?  A comment in
the code would be especially good so anyone modifying the code
understands this in future.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)