From: Andreas Schwab <schwab@linux-m68k.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: tongtiangen@huawei.com, jszhang3@mail.ustc.edu.cn,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next v2] riscv: add VMAP_STACK overflow detection
Date: Thu, 22 Jul 2021 11:02:10 +0200 [thread overview]
Message-ID: <87k0lizppp.fsf@igel.home> (raw)
In-Reply-To: <mhng-e14c3232-cc4d-4146-8c93-c60ec81ed272@palmerdabbelt-glaptop> (Palmer Dabbelt's message of "Wed, 21 Jul 2021 23:12:20 -0700 (PDT)")
On Jul 21 2021, Palmer Dabbelt wrote:
> On Mon, 19 Jul 2021 00:23:06 PDT (-0700), schwab@linux-m68k.org wrote:
>> On Jul 19 2021, tongtiangen wrote:
>>
>>> On 2021/7/17 14:55, Andreas Schwab wrote:
>>>> Please use
>>>> https://download.opensuse.org/repositories/home:/Andreas_Schwab:/riscv:/jeos/images/openSUSE-Tumbleweed-RISC-V-JeOS-efi.riscv64.raw.xz
>>>> and run it in qemu with u-boot as kernel.
>>>>
>>>> Andreas.
>>>>
>>>
>>> Hi andreas:
>>> I used today's latest mainline code and .config provided by you, and I
>>> can't reproduce this panic.
>>
>> Did you test it like I said above?
>>
>> Andreas.
>
> I'm getting this on and off, with just
> CONFIG_VMAP_STACK=y
>
> on top of defconfig, when running on QEMU. It's not showing up right now:
> I'd thought it was an issue with that initrd patch, but it went away when
> I re-ran the tests so I'm guessing it's something non-deterministic. I'll
> try to take a look if it comes back.
The crash happens reliably with the image above.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@linux-m68k.org>
To: Palmer Dabbelt <palmer@dabbelt.com>
Cc: tongtiangen@huawei.com, jszhang3@mail.ustc.edu.cn,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next v2] riscv: add VMAP_STACK overflow detection
Date: Thu, 22 Jul 2021 11:02:10 +0200 [thread overview]
Message-ID: <87k0lizppp.fsf@igel.home> (raw)
In-Reply-To: <mhng-e14c3232-cc4d-4146-8c93-c60ec81ed272@palmerdabbelt-glaptop> (Palmer Dabbelt's message of "Wed, 21 Jul 2021 23:12:20 -0700 (PDT)")
On Jul 21 2021, Palmer Dabbelt wrote:
> On Mon, 19 Jul 2021 00:23:06 PDT (-0700), schwab@linux-m68k.org wrote:
>> On Jul 19 2021, tongtiangen wrote:
>>
>>> On 2021/7/17 14:55, Andreas Schwab wrote:
>>>> Please use
>>>> https://download.opensuse.org/repositories/home:/Andreas_Schwab:/riscv:/jeos/images/openSUSE-Tumbleweed-RISC-V-JeOS-efi.riscv64.raw.xz
>>>> and run it in qemu with u-boot as kernel.
>>>>
>>>> Andreas.
>>>>
>>>
>>> Hi andreas:
>>> I used today's latest mainline code and .config provided by you, and I
>>> can't reproduce this panic.
>>
>> Did you test it like I said above?
>>
>> Andreas.
>
> I'm getting this on and off, with just
> CONFIG_VMAP_STACK=y
>
> on top of defconfig, when running on QEMU. It's not showing up right now:
> I'd thought it was an issue with that initrd patch, but it went away when
> I re-ran the tests so I'm guessing it's something non-deterministic. I'll
> try to take a look if it comes back.
The crash happens reliably with the image above.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2021-07-22 9:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 3:28 [PATCH -next v2] riscv: add VMAP_STACK overflow detection Tong Tiangen
2021-06-21 3:28 ` Tong Tiangen
2021-07-06 20:24 ` Palmer Dabbelt
2021-07-06 20:24 ` Palmer Dabbelt
2021-07-15 16:22 ` Andreas Schwab
2021-07-15 16:22 ` Andreas Schwab
2021-07-16 12:53 ` Jisheng Zhang
2021-07-16 12:53 ` Jisheng Zhang
2021-07-16 15:53 ` Andreas Schwab
2021-07-16 15:53 ` Andreas Schwab
2021-07-17 2:18 ` Jisheng Zhang
2021-07-17 2:18 ` Jisheng Zhang
2021-07-17 6:55 ` Andreas Schwab
2021-07-17 6:55 ` Andreas Schwab
2021-07-19 3:27 ` tongtiangen
2021-07-19 3:27 ` tongtiangen
2021-07-19 7:23 ` Andreas Schwab
2021-07-19 7:23 ` Andreas Schwab
2021-07-22 6:12 ` Palmer Dabbelt
2021-07-22 6:12 ` Palmer Dabbelt
2021-07-22 8:35 ` Atish Patra
2021-07-22 8:35 ` Atish Patra
2021-07-22 13:37 ` Jisheng Zhang
2021-07-22 13:37 ` Jisheng Zhang
2021-07-22 14:24 ` Jisheng Zhang
2021-07-22 14:24 ` Jisheng Zhang
2021-07-22 15:42 ` Andreas Schwab
2021-07-22 15:42 ` Andreas Schwab
2021-07-22 23:54 ` Jisheng Zhang
2021-07-22 23:54 ` Jisheng Zhang
2021-07-23 1:36 ` tongtiangen
2021-07-23 1:36 ` tongtiangen
2021-07-23 4:29 ` Jisheng Zhang
2021-07-23 4:29 ` Jisheng Zhang
2021-07-23 4:40 ` Jisheng Zhang
2021-07-23 4:40 ` Jisheng Zhang
2021-07-23 6:49 ` tongtiangen
2021-07-22 9:02 ` Andreas Schwab [this message]
2021-07-22 9:02 ` Andreas Schwab
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=87k0lizppp.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=aou@eecs.berkeley.edu \
--cc=jszhang3@mail.ustc.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=tongtiangen@huawei.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 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.