All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Song Shuai <songshuaishuai@tinylab.org>
Cc: linux-riscv@lists.infradead.org, takakura@valinux.co.jp,
	alex@ghiti.fr, paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, bhe@redhat.com, akpm@linux-foundation.org,
	guoren@kernel.org, xianting.tian@linux.alibaba.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 -fixes] riscv: kexec: Avoid deadlock in kexec crash path
Date: Thu, 04 Jul 2024 13:10:56 +0000	[thread overview]
Message-ID: <172009865675.17306.18375440466203340384.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240626023316.539971-1-songshuaishuai@tinylab.org>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed, 26 Jun 2024 10:33:16 +0800 you wrote:
> If the kexec crash code is called in the interrupt context, the
> machine_kexec_mask_interrupts() function will trigger a deadlock while
> trying to acquire the irqdesc spinlock and then deactivate irqchip in
> irq_set_irqchip_state() function.
> 
> Unlike arm64, riscv only requires irq_eoi handler to complete EOI and
> keeping irq_set_irqchip_state() will only leave this possible deadlock
> without any use. So we simply remove it.
> 
> [...]

Here is the summary with links:
  - [V2,-fixes] riscv: kexec: Avoid deadlock in kexec crash path
    https://git.kernel.org/riscv/c/c562ba719df5

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: Song Shuai <songshuaishuai@tinylab.org>
Cc: linux-riscv@lists.infradead.org, takakura@valinux.co.jp,
	alex@ghiti.fr, paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, bhe@redhat.com, akpm@linux-foundation.org,
	guoren@kernel.org, xianting.tian@linux.alibaba.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 -fixes] riscv: kexec: Avoid deadlock in kexec crash path
Date: Thu, 04 Jul 2024 13:10:56 +0000	[thread overview]
Message-ID: <172009865675.17306.18375440466203340384.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240626023316.539971-1-songshuaishuai@tinylab.org>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed, 26 Jun 2024 10:33:16 +0800 you wrote:
> If the kexec crash code is called in the interrupt context, the
> machine_kexec_mask_interrupts() function will trigger a deadlock while
> trying to acquire the irqdesc spinlock and then deactivate irqchip in
> irq_set_irqchip_state() function.
> 
> Unlike arm64, riscv only requires irq_eoi handler to complete EOI and
> keeping irq_set_irqchip_state() will only leave this possible deadlock
> without any use. So we simply remove it.
> 
> [...]

Here is the summary with links:
  - [V2,-fixes] riscv: kexec: Avoid deadlock in kexec crash path
    https://git.kernel.org/riscv/c/c562ba719df5

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



  parent reply	other threads:[~2024-07-04 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26  2:33 [PATCH V2 -fixes] riscv: kexec: Avoid deadlock in kexec crash path Song Shuai
2024-06-26  2:33 ` Song Shuai
2024-06-26  6:32 ` [V2,-fixes] " takakura
2024-06-26  6:32   ` takakura
2024-07-04 13:10 ` patchwork-bot+linux-riscv [this message]
2024-07-04 13:10   ` [PATCH V2 -fixes] " 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=172009865675.17306.18375440466203340384.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=bhe@redhat.com \
    --cc=guoren@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=songshuaishuai@tinylab.org \
    --cc=takakura@valinux.co.jp \
    --cc=xianting.tian@linux.alibaba.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.