All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Nam Cao <namcao@linutronix.de>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	samuel.holland@sifive.com, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] riscv: Fix kernel crash due to PR_SET_TAGGED_ADDR_CTRL
Date: Thu, 08 May 2025 16:52:10 +0000	[thread overview]
Message-ID: <174672313099.2976395.17884540800538496278.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250504101920.3393053-1-namcao@linutronix.de>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Alexandre Ghiti <alexghiti@rivosinc.com>:

On Sun,  4 May 2025 12:19:20 +0200 you wrote:
> When userspace does PR_SET_TAGGED_ADDR_CTRL, but Supm extension is not
> available, the kernel crashes:
> 
> Oops - illegal instruction [#1]
>     [snip]
> epc : set_tagged_addr_ctrl+0x112/0x15a
>  ra : set_tagged_addr_ctrl+0x74/0x15a
> epc : ffffffff80011ace ra : ffffffff80011a30 sp : ffffffc60039be10
>     [snip]
> status: 0000000200000120 badaddr: 0000000010a79073 cause: 0000000000000002
>     set_tagged_addr_ctrl+0x112/0x15a
>     __riscv_sys_prctl+0x352/0x73c
>     do_trap_ecall_u+0x17c/0x20c
>     andle_exception+0x150/0x15c
> 
> [...]

Here is the summary with links:
  - riscv: Fix kernel crash due to PR_SET_TAGGED_ADDR_CTRL
    https://git.kernel.org/riscv/c/ae08d55807c0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
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: patchwork-bot+linux-riscv@kernel.org
To: Nam Cao <namcao@linutronix.de>
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	samuel.holland@sifive.com, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] riscv: Fix kernel crash due to PR_SET_TAGGED_ADDR_CTRL
Date: Thu, 08 May 2025 16:52:10 +0000	[thread overview]
Message-ID: <174672313099.2976395.17884540800538496278.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250504101920.3393053-1-namcao@linutronix.de>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Alexandre Ghiti <alexghiti@rivosinc.com>:

On Sun,  4 May 2025 12:19:20 +0200 you wrote:
> When userspace does PR_SET_TAGGED_ADDR_CTRL, but Supm extension is not
> available, the kernel crashes:
> 
> Oops - illegal instruction [#1]
>     [snip]
> epc : set_tagged_addr_ctrl+0x112/0x15a
>  ra : set_tagged_addr_ctrl+0x74/0x15a
> epc : ffffffff80011ace ra : ffffffff80011a30 sp : ffffffc60039be10
>     [snip]
> status: 0000000200000120 badaddr: 0000000010a79073 cause: 0000000000000002
>     set_tagged_addr_ctrl+0x112/0x15a
>     __riscv_sys_prctl+0x352/0x73c
>     do_trap_ecall_u+0x17c/0x20c
>     andle_exception+0x150/0x15c
> 
> [...]

Here is the summary with links:
  - riscv: Fix kernel crash due to PR_SET_TAGGED_ADDR_CTRL
    https://git.kernel.org/riscv/c/ae08d55807c0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2025-05-08 17:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-04 10:19 [PATCH] riscv: Fix kernel crash due to PR_SET_TAGGED_ADDR_CTRL Nam Cao
2025-05-04 10:19 ` Nam Cao
2025-05-05 16:02 ` Alexandre Ghiti
2025-05-05 16:02   ` Alexandre Ghiti
2025-05-05 16:07   ` Nam Cao
2025-05-05 16:07     ` Nam Cao
2025-05-05 19:27     ` Alexandre Ghiti
2025-05-05 19:27       ` Alexandre Ghiti
2025-05-06 16:31       ` Alexandre Ghiti
2025-05-06 16:31         ` Alexandre Ghiti
2025-05-06 22:29         ` Samuel Holland
2025-05-06 22:29           ` Samuel Holland
2025-05-07 18:05           ` Nam Cao
2025-05-07 18:05             ` Nam Cao
2025-05-08 16:52 ` patchwork-bot+linux-riscv [this message]
2025-05-08 16:52   ` patchwork-bot+linux-riscv

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=174672313099.2976395.17884540800538496278.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=namcao@linutronix.de \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=samuel.holland@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 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.