From: Helge Deller <deller@gmx.de>
To: Mikulas Patocka <mpatocka@redhat.com>,
John David Anglin <dave.anglin@bell.net>
Cc: John David Anglin <dave@parisc-linux.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH v2] parisc: fix a possible DMA corruption
Date: Sun, 28 Jul 2024 15:25:14 +0200 [thread overview]
Message-ID: <c629285c-6113-417d-ae29-18345b2533d0@gmx.de> (raw)
In-Reply-To: <a233f8cd-ec48-3d2c-cfca-d863bb9912f5@redhat.com>
On 7/27/24 20:22, Mikulas Patocka wrote:
> ARCH_DMA_MINALIGN was defined as 16 - this is too small - it may be
> possible that two unrelated 16-byte allocations share a cache line. If
> one of these allocations is written using DMA and the other is written
> using cached write, the value that was written with DMA may be
> corrupted.
>
> This commit changes ARCH_DMA_MINALIGN to be 128 on PA20 and 32 on PA1.1 -
> that's the largest possible cache line size.
>
> As different parisc microarchitectures have different cache line size, we
> define arch_slab_minalign(), cache_line_size() and
> dma_get_cache_alignment() so that the kernel may tune slab cache
> parameters dynamically, based on the detected cache line size.
>
> Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
> Cc: stable@vger.kernel.org
applied.
Thanks!
Helge
>
> ---
> arch/parisc/Kconfig | 1 +
> arch/parisc/include/asm/cache.h | 11 ++++++++++-
> 2 files changed, 11 insertions(+), 1 deletion(-)
>
> Index: linux-6.10/arch/parisc/include/asm/cache.h
> ===================================================================
> --- linux-6.10.orig/arch/parisc/include/asm/cache.h 2023-09-18 11:33:40.000000000 +0200
> +++ linux-6.10/arch/parisc/include/asm/cache.h 2024-07-27 19:28:18.000000000 +0200
> @@ -20,7 +20,16 @@
>
> #define SMP_CACHE_BYTES L1_CACHE_BYTES
>
> -#define ARCH_DMA_MINALIGN L1_CACHE_BYTES
> +#ifndef CONFIG_PA20
> +#define ARCH_DMA_MINALIGN 32
> +#else
> +#define ARCH_DMA_MINALIGN 128
> +#endif
> +#define ARCH_KMALLOC_MINALIGN 16 /* ldcw requires 16-byte alignment */
> +
> +#define arch_slab_minalign() ((unsigned)dcache_stride)
> +#define cache_line_size() dcache_stride
> +#define dma_get_cache_alignment cache_line_size
>
> #define __read_mostly __section(".data..read_mostly")
>
> Index: linux-6.10/arch/parisc/Kconfig
> ===================================================================
> --- linux-6.10.orig/arch/parisc/Kconfig 2024-07-23 20:35:34.000000000 +0200
> +++ linux-6.10/arch/parisc/Kconfig 2024-07-26 19:41:15.000000000 +0200
> @@ -20,6 +20,7 @@ config PARISC
> select ARCH_SUPPORTS_HUGETLBFS if PA20
> select ARCH_SUPPORTS_MEMORY_FAILURE
> select ARCH_STACKWALK
> + select ARCH_HAS_CACHE_LINE_SIZE
> select ARCH_HAS_DEBUG_VM_PGTABLE
> select HAVE_RELIABLE_STACKTRACE
> select DMA_OPS
>
prev parent reply other threads:[~2024-07-28 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-27 10:06 [PATCH] parisc: fix a possible DMA corruption Mikulas Patocka
2024-07-27 14:39 ` John David Anglin
2024-07-27 18:22 ` [PATCH v2] " Mikulas Patocka
2024-07-28 13:25 ` Helge Deller [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=c629285c-6113-417d-ae29-18345b2533d0@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dave.anglin@bell.net \
--cc=dave@parisc-linux.org \
--cc=linux-parisc@vger.kernel.org \
--cc=mpatocka@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox