All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: Denis Ivanov <denis.ivanov@cloudbear.ru>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>, Dao Lu <daolu@rivosinc.com>,
	linux-riscv@lists.infradead.org
Subject: Re: Bug report: cpu_relax call from vdso space
Date: Tue, 18 Oct 2022 22:19:21 +0800	[thread overview]
Message-ID: <Y0616eIDlrlGwF3a@xhacker> (raw)
In-Reply-To: <3815b200-a9e2-a3db-c7f1-1e3f86dbab3f@cloudbear.ru>

On Sat, Oct 15, 2022 at 10:08:55AM +0300, Denis Ivanov wrote:
> Hello,
> 
> Segmentation fault may be raised from cpu_relax()
> (arch/riscv/include/asm/vdso/processor.h).
> 
> cpu_relax() may be called from vDSO functions (ex: __vdso_clock_gettime).
> This means that global 'riscv_isa_ext_keys' variable must not be used in
> cpu_relax() directly.

Hi,

Could you please share how to reproduce the Segment fault with
cpu_relax()? 

Thanks

> 
> Use of this array was added to cpu_relax() in
> https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/commit/?h=fixes&id=8eb060e10185cfc97ef0200d197ec246ba0f9f8c
> 
> Denis Ivanov
> 
> 
> _______________________________________________
> linux-riscv mailing list
> linux-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-riscv

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

  parent reply	other threads:[~2022-10-18 14:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15  7:08 Bug report: cpu_relax call from vdso space Denis Ivanov
2022-10-17 17:54 ` Atish Patra
2022-10-18  8:37   ` Denis Ivanov
2022-10-18 14:19 ` Jisheng Zhang [this message]
2022-10-18 16:14   ` Denis Ivanov

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=Y0616eIDlrlGwF3a@xhacker \
    --to=jszhang@kernel.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=daolu@rivosinc.com \
    --cc=denis.ivanov@cloudbear.ru \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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.