Re: syzkaller on risc-v

From: Andreas Schwab <schwab@suse.de>
To: David Abdurachmanov <david.abdurachmanov@gmail.com>
Cc: "Albert Ou" <aou@eecs.berkeley.edu>,
	"Björn Töpel" <bjorn.topel@gmail.com>,
	syzkaller <syzkaller@googlegroups.com>,
	"Palmer Dabbelt" <palmer@dabbelt.com>,
	"Paul Walmsley" <paul.walmsley@sifive.com>,
	"Colin Ian King" <colin.king@canonical.com>,
	"Tobias Klauser" <tklauser@distanz.ch>,
	linux-riscv <linux-riscv@lists.infradead.org>,
	"Dmitry Vyukov" <dvyukov@google.com>
Subject: Re: syzkaller on risc-v
Date: Tue, 30 Jun 2020 16:55:21 +0200	[thread overview]
Message-ID: <mvmmu4kli1y.fsf@suse.de> (raw)
In-Reply-To: <CAEn-LToeQXFnuG=Z17nSHKD872+Hmep1DM1bhs1Og_deU9+OcA@mail.gmail.com> (David Abdurachmanov's message of "Tue, 30 Jun 2020 16:57:12 +0300")

On Jun 30 2020, David Abdurachmanov wrote:

> On Tue, Jun 30, 2020 at 4:38 PM Colin Ian King <colin.king@canonical.com> wrote:
>>
>> I believe I'm also seeing some potential stack smashing issues in the
>> lua engine in ZFS on risc-v. It is taking a while for me to debug, but I
>> don't see the failure on other arches.  Is there a way to bump the stack
>> size up temporarily to test with larger stacks on risc-v?
>
> Dmitry wrote on the original email that the follow solves issues with
> KCOV enabled:
>
> --- a/arch/riscv/include/asm/thread_info.h
> +++ b/arch/riscv/include/asm/thread_info.h
> -#define THREAD_SIZE_ORDER      (1)
> +#define THREAD_SIZE_ORDER      (2)

I think riscv should follow mips and use 16Kb stacks for 64-bit.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv