All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang3@mail.ustc.edu.cn>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Tong Tiangen <tongtiangen@huawei.com>, <palmerdabbelt@google.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <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: Sat, 17 Jul 2021 10:18:05 +0800	[thread overview]
Message-ID: <20210717101805.2afabacb@xhacker> (raw)
In-Reply-To: <871r7yz241.fsf@igel.home>

On Fri, 16 Jul 2021 17:53:50 +0200
Andreas Schwab <schwab@linux-m68k.org> wrote:

> On Jul 16 2021, Jisheng Zhang wrote:
> 
> > I can't reproduce the panic error. Mind to share your .config?  
> 
> https://github.com/openSUSE/kernel-source/blob/master/config/riscv64/default
> 
> Andreas.
> 

Looks a bit strange. With the above .config, I still can't reproduce the panic
either by

cat /proc/PID/wchan

or

cat /proc/PID/stat

I use the latest linus tree w/o any patch. I noticed that some SUSE_* config
in the .config file, is it possible that you applied some patches? If so,
can you please try the lasest linus tree w/o any patch?

Thanks


WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang3@mail.ustc.edu.cn>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Tong Tiangen <tongtiangen@huawei.com>, <palmerdabbelt@google.com>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <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: Sat, 17 Jul 2021 10:18:05 +0800	[thread overview]
Message-ID: <20210717101805.2afabacb@xhacker> (raw)
In-Reply-To: <871r7yz241.fsf@igel.home>

On Fri, 16 Jul 2021 17:53:50 +0200
Andreas Schwab <schwab@linux-m68k.org> wrote:

> On Jul 16 2021, Jisheng Zhang wrote:
> 
> > I can't reproduce the panic error. Mind to share your .config?  
> 
> https://github.com/openSUSE/kernel-source/blob/master/config/riscv64/default
> 
> Andreas.
> 

Looks a bit strange. With the above .config, I still can't reproduce the panic
either by

cat /proc/PID/wchan

or

cat /proc/PID/stat

I use the latest linus tree w/o any patch. I noticed that some SUSE_* config
in the .config file, is it possible that you applied some patches? If so,
can you please try the lasest linus tree w/o any patch?

Thanks


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

  reply	other threads:[~2021-07-17  2:24 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 [this message]
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
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=20210717101805.2afabacb@xhacker \
    --to=jszhang3@mail.ustc.edu.cn \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=palmerdabbelt@google.com \
    --cc=paul.walmsley@sifive.com \
    --cc=schwab@linux-m68k.org \
    --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.