public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	"Alexandre Ghiti" <alexghiti@rivosinc.com>,
	"Björn Töpel" <bjorn@rivosinc.com>,
	"Palmer Dabbelt" <palmer@rivosinc.com>,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org
Subject: Re: [PATCH AUTOSEL 6.3 5/7] riscv: Unconditionnally select KASAN_VMALLOC if KASAN
Date: Thu, 18 May 2023 13:45:23 -0400	[thread overview]
Message-ID: <ZGZkM98lOHUEF4mA@sashalap> (raw)
In-Reply-To: <bea1128b-903c-a7d0-9929-d9667999bb6d@ghiti.fr>

On Fri, May 12, 2023 at 11:51:03AM +0200, Alexandre Ghiti wrote:
>Hi Sasha,
>
>On 5/9/23 05:54, Sasha Levin wrote:
>>From: Alexandre Ghiti <alexghiti@rivosinc.com>
>>
>>[ Upstream commit 864046c512c2cd8418dc928b91981fb12a80396c ]
>>
>>If KASAN is enabled, VMAP_STACK depends on KASAN_VMALLOC so enable
>>KASAN_VMALLOC with KASAN so that we can enable VMAP_STACK by default.
>>
>>Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>
>>Reviewed-by: Björn Töpel <bjorn@rivosinc.com>
>>Link: https://lore.kernel.org/r/20230203075232.274282-7-alexghiti@rivosinc.com
>>Signed-off-by: Palmer Dabbelt <palmer@rivosinc.com>
>>Signed-off-by: Sasha Levin <sashal@kernel.org>
>>---
>>  arch/riscv/Kconfig | 1 +
>>  1 file changed, 1 insertion(+)
>>
>>diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
>>index eb7f29a412f87..d6aad84efb95e 100644
>>--- a/arch/riscv/Kconfig
>>+++ b/arch/riscv/Kconfig
>>@@ -118,6 +118,7 @@ config RISCV
>>  	select HAVE_SYSCALL_TRACEPOINTS
>>  	select IRQ_DOMAIN
>>  	select IRQ_FORCED_THREADING
>>+	select KASAN_VMALLOC if KASAN
>>  	select MODULES_USE_ELF_RELA if MODULES
>>  	select MODULE_SECTIONS if MODULES
>>  	select OF
>
>
>KASAN_VMALLOC is broken for any kernel < 6.4, so this one should not 
>be backported to any kernel (5.15, 6.1, 6.2, 6.3).

Ack, dropped. Thanks!

-- 
Thanks,
Sasha

  reply	other threads:[~2023-05-18 17:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09  3:54 [PATCH AUTOSEL 6.3 1/7] powerpc: Use of_property_present() for testing DT property presence Sasha Levin
2023-05-09  3:54 ` [PATCH AUTOSEL 6.3 2/7] sched: Fix KCSAN noinstr violation Sasha Levin
2023-05-09  3:54 ` [PATCH AUTOSEL 6.3 3/7] lkdtm/stackleak: Fix " Sasha Levin
2023-05-09  3:54 ` [PATCH AUTOSEL 6.3 4/7] riscv: Fix EFI stub usage of KASAN instrumented strcmp function Sasha Levin
2023-05-09  3:54 ` [PATCH AUTOSEL 6.3 5/7] riscv: Unconditionnally select KASAN_VMALLOC if KASAN Sasha Levin
2023-05-12  9:51   ` Alexandre Ghiti
2023-05-18 17:45     ` Sasha Levin [this message]
2023-05-09  3:54 ` [PATCH AUTOSEL 6.3 6/7] powerpc/fsl_uli1575: Allow to disable FSL_ULI1575 support Sasha Levin
2023-05-09  4:18   ` Randy Dunlap
2023-05-09  7:14     ` Michael Ellerman
2023-05-09  7:18       ` Pali Rohár
2023-05-18 17:47         ` Sasha Levin
2023-05-09  3:54 ` [PATCH AUTOSEL 6.3 7/7] recordmcount: Fix memory leaks in the uwrite function Sasha Levin

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=ZGZkM98lOHUEF4mA@sashalap \
    --to=sashal@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=alexghiti@rivosinc.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bjorn@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.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