Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Clement LE GOFFIC <clement.legoffic@foss.st.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Russell King <linux@armlinux.org.uk>, Kees Cook <kees@kernel.org>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	Mark Brown <broonie@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Ard Biesheuvel <ardb@kernel.org>
Cc: Antonio Borneo <antonio.borneo@foss.st.com>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v3 1/2] ARM: ioremap: Sync PGDs for VMALLOC shadow
Date: Thu, 17 Oct 2024 16:19:57 +0200	[thread overview]
Message-ID: <69f71ac8-4ba6-46ed-b2ab-e575dcada47b@foss.st.com> (raw)
In-Reply-To: <20241017-arm-kasan-vmalloc-crash-v3-1-d2a34cd5b663@linaro.org>

On 10/17/24 14:59, Linus Walleij wrote:
> [...]
>   
> +static unsigned long arm_kasan_mem_to_shadow(unsigned long addr)
> +{
> +	return (unsigned long)kasan_mem_to_shadow((void *)addr);
> +}
> +

`kasan_mem_to_shadow` function symbol is only exported with :
CONFIG_KASAN_GENERIC or defined(CONFIG_KASAN_SW_TAGS) from kasan.h

To me, the if condition you added below should be expanded with those 
two macros.

> [...]
>   void __check_vmalloc_seq(struct mm_struct *mm)
>   {
>   	int seq;
>   
>   	do {
>   		seq = atomic_read(&init_mm.context.vmalloc_seq);
> -		memcpy(pgd_offset(mm, VMALLOC_START),
> -		       pgd_offset_k(VMALLOC_START),
> -		       sizeof(pgd_t) * (pgd_index(VMALLOC_END) -
> -					pgd_index(VMALLOC_START)));
> +		memcpy_pgd(mm, VMALLOC_START, VMALLOC_END);
> +		if (IS_ENABLED(CONFIG_KASAN_VMALLOC)) {
> +			unsigned long start =
> +				arm_kasan_mem_to_shadow(VMALLOC_START);
> +			unsigned long end =
> +				arm_kasan_mem_to_shadow(VMALLOC_END);
> +			memcpy_pgd(mm, start, end);
> +		}
>   		/*
>   		 * Use a store-release so that other CPUs that observe the
>   		 * counter's new value are guaranteed to see the results of the
>
Otherwise it compiles with KASAN enabled, I am running some tests with 
your patches.

Regards,

Clément

  reply	other threads:[~2024-10-17 14:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 12:59 [PATCH v3 0/2] Fix KASAN crash when using KASAN_VMALLOC Linus Walleij
2024-10-17 12:59 ` [PATCH v3 1/2] ARM: ioremap: Sync PGDs for VMALLOC shadow Linus Walleij
2024-10-17 14:19   ` Clement LE GOFFIC [this message]
2024-10-17 19:00     ` Linus Walleij
2024-10-21 12:09       ` Clement LE GOFFIC
2024-10-21 12:46         ` Linus Walleij
2024-10-24 21:58         ` Linus Walleij
2024-10-25  9:24           ` Clement LE GOFFIC
2024-10-25 11:04             ` Linus Walleij
2024-10-25 20:57               ` Linus Walleij
2024-10-29 15:00                 ` Clement LE GOFFIC
2024-10-29 21:32                   ` Linus Walleij
2024-10-17 12:59 ` [PATCH v3 2/2] ARM: entry: Do a dummy read from VMAP shadow Linus Walleij

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=69f71ac8-4ba6-46ed-b2ab-e575dcada47b@foss.st.com \
    --to=clement.legoffic@foss.st.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=antonio.borneo@foss.st.com \
    --cc=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=kees@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=linux@armlinux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox