Skip to content

[PW_SID:1073221] riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated#1673

Closed
linux-riscv-bot wants to merge 1 commit into
workflow__riscv__fixesfrom
pw1073221
Closed

[PW_SID:1073221] riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated#1673
linux-riscv-bot wants to merge 1 commit into
workflow__riscv__fixesfrom
pw1073221

Conversation

@linux-riscv-bot
Copy link
Copy Markdown

PR for series 1073221 applied to workflow__riscv__fixes

Name: riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated
URL: https://patchwork.kernel.org/project/linux-riscv/list/?series=1073221
Version: 1

init_irq_stacks() and init_irq_scs() may fail when arch_alloc_vmap_stack
or scs_alloc return NULL. Return -ENOMEM from both and call panic() once
from init_IRQ(), covering per-CPU IRQ stacks and shadow IRQ stacks
consistently.

Signed-off-by: Osama Abdelkader <osama.abdelkader@gmail.com>
Signed-off-by: Linux RISC-V bot <linux.riscv.bot@gmail.com>
@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
build-rv32-defconfig
Desc: Builds riscv32 defconfig
Duration: 136.34 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
build-rv64-clang-allmodconfig
Desc: Builds riscv64 allmodconfig with Clang, and checks for errors and added warnings
Duration: 1110.74 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
build-rv64-gcc-allmodconfig
Desc: Builds riscv64 allmodconfig with GCC, and checks for errors and added warnings
Duration: 1622.96 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
build-rv64-nommu-k210-defconfig
Desc: Builds riscv64 defconfig with NOMMU for K210
Duration: 26.95 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
build-rv64-nommu-k210-virt
Desc: Builds riscv64 defconfig with NOMMU for the virt platform
Duration: 28.37 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
checkpatch
Desc: Runs checkpatch.pl on the patch
Duration: 0.92 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
dtb-warn-rv64
Desc: Checks for Device Tree warnings/errors
Duration: 84.08 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
header-inline
Desc: Detects static functions without inline keyword in header files
Duration: 0.23 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
kdoc
Desc: Detects for kdoc errors
Duration: 0.91 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
module-param
Desc: Detect module_param changes
Duration: 0.25 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
verify-fixes
Desc: Verifies that the Fixes: tags exist
Duration: 0.23 seconds
Result: PASS

@linux-riscv-bot
Copy link
Copy Markdown
Author

Patch 1: "riscv: panic from init_IRQ if IRQ handler stacks cannot be allocated"
verify-signedoff
Desc: Verifies that Signed-off-by: tags are correct
Duration: 0.30 seconds
Result: PASS

@linux-riscv-bot linux-riscv-bot deleted the pw1073221 branch April 2, 2026 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants