From: patchwork-bot+linux-riscv@kernel.org
To: <wang.yaxin@zte.com.cn>
Cc: linux-riscv@lists.infradead.org, anup@brainfault.org,
tglx@linutronix.de, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, zhang.run@zte.com.cn,
hu.shengming@zte.com.cn, zhang.anmeng@zte.com.cn,
luo.haiyang@zte.com.cn, alex@ghiti.fr,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH linux-next] irqchip/riscv-imsic: Revert "Remove redundant irq_data lookups"
Date: Mon, 26 Jan 2026 04:21:48 +0000 [thread overview]
Message-ID: <176940130834.4057692.5469884123687376656.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260113111930821RrC26avITHWSFCN0bYbgI@zte.com.cn>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Thomas Gleixner <tglx@kernel.org>:
On Tue, 13 Jan 2026 11:19:30 +0800 (CST) you wrote:
> From: Luo Haiyang <luo.haiyang@zte.com.cn>
>
> Commit c475c0b71314("irqchip/riscv-imsic: Remove redundant irq_data
> lookups") leads a NULL pointer deference in imsic_msi_update_msg().
>
> When QEMU is launched with the following additional boot parameters:
> "-device virtio-blk-pci,drive=disk1 \
> -drive file=disk.qcow2,if=none,id=disk1,format=qcow2 \"
>
> [...]
Here is the summary with links:
- [linux-next] irqchip/riscv-imsic: Revert "Remove redundant irq_data lookups"
https://git.kernel.org/riscv/c/f2edf797dab1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-26 4:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 3:19 wang.yaxin
2026-01-13 8:59 ` [tip: irq/urgent] " tip-bot2 for Luo Haiyang
2026-01-26 4:21 ` patchwork-bot+linux-riscv [this message]
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=176940130834.4057692.5469884123687376656.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=hu.shengming@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luo.haiyang@zte.com.cn \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=tglx@linutronix.de \
--cc=wang.yaxin@zte.com.cn \
--cc=zhang.anmeng@zte.com.cn \
--cc=zhang.run@zte.com.cn \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome