All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: stable@vger.kernel.org, Will Deacon <will@kernel.org>
Subject: Re: [PATCH stable-5.15] arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer
Date: Thu, 23 Jun 2022 18:17:40 +0200	[thread overview]
Message-ID: <YrSSJMKL/GL45GA3@kroah.com> (raw)
In-Reply-To: <20220623154412.1117070-1-catalin.marinas@arm.com>

On Thu, Jun 23, 2022 at 04:44:12PM +0100, Catalin Marinas wrote:
> From: Will Deacon <will@kernel.org>
> 
> commit c50f11c6196f45c92ca48b16a5071615d4ae0572 upstream.
> 
> Invalidating the buffer memory in arch_sync_dma_for_device() for
> FROM_DEVICE transfers
> 
> When using the streaming DMA API to map a buffer prior to inbound
> non-coherent DMA (i.e. DMA_FROM_DEVICE), we invalidate any dirty CPU
> cachelines so that they will not be written back during the transfer and
> corrupt the buffer contents written by the DMA. This, however, poses two
> potential problems:
> 
>   (1) If the DMA transfer does not write to every byte in the buffer,
>       then the unwritten bytes will contain stale data once the transfer
>       has completed.
> 
>   (2) If the buffer has a virtual alias in userspace, then stale data
>       may be visible via this alias during the period between performing
>       the cache invalidation and the DMA writes landing in memory.
> 
> Address both of these issues by cleaning (aka writing-back) the dirty
> lines in arch_sync_dma_for_device(DMA_FROM_DEVICE) instead of discarding
> them using invalidation.
> 
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: Russell King <linux@armlinux.org.uk>
> Cc: <stable@vger.kernel.org>
> Link: https://lore.kernel.org/r/20220606152150.GA31568@willie-the-truck
> Signed-off-by: Will Deacon <will@kernel.org>
> Reviewed-by: Ard Biesheuvel <ardb@kernel.org>
> Link: https://lore.kernel.org/r/20220610151228.4562-2-will@kernel.org
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> ---
>  arch/arm64/mm/cache.S | 2 --
>  1 file changed, 2 deletions(-)

All now queued up, thanks.

greg k-h

      reply	other threads:[~2022-06-23 16:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 15:44 [PATCH stable-5.15] arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer Catalin Marinas
2022-06-23 16:17 ` Greg Kroah-Hartman [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=YrSSJMKL/GL45GA3@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=stable@vger.kernel.org \
    --cc=will@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.