From: sashiko-bot@kernel.org
To: "Boris Brezillon" <boris.brezillon@collabora.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3 3/7] drm/panthor: Replace the panthor_irq macro machinery by inline helpers
Date: Tue, 23 Jun 2026 13:02:32 +0000 [thread overview]
Message-ID: <20260623130232.862511F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260623-panthor-signal-from-irq-v3-3-2ece396f8ee0@collabora.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
Pre-existing issues:
- [High] Hardware interrupts are unmasked before the OS interrupt handler is successfully registered, risking an unhandled IRQ storm.
--
commit 4e867b9890a5ecc61feefa09f80bbc3aaddcd675
Author: Boris Brezillon <boris.brezillon@collabora.com>
drm/panthor: Replace the panthor_irq macro machinery by inline helpers
This commit removes the panthor_irq macro generation logic and replaces it
with inline helpers to rely on compiler optimization. It also refactors the
prototype of IRQ handlers to take struct panthor_irq instead of struct
panthor_device.
> diff --git a/drivers/gpu/drm/panthor/panthor_device.h b/drivers/gpu/drm/panthor/panthor_device.h
> --- a/drivers/gpu/drm/panthor/panthor_device.h
> +++ b/drivers/gpu/drm/panthor/panthor_device.h
[ ... ]
> +static inline int
> +panthor_irq_request(struct panthor_device *ptdev, struct panthor_irq *pirq,
> + int irq, u32 mask, void __iomem *iomem, const char *name,
> + irqreturn_t (*threaded_handler)(int, void *data))
> +{
[ ... ]
> + panthor_irq_resume(pirq);
> + return devm_request_threaded_irq(ptdev->base.dev, irq,
> + panthor_irq_default_raw_handler,
> + threaded_handler,
> + IRQF_SHARED, full_name, pirq);
> }
[Severity: High]
This is a pre-existing issue, but by calling panthor_irq_resume() before
devm_request_threaded_irq(), does this leave a window where the hardware
interrupt is unmasked before the OS handler is successfully registered?
If the device asserts an interrupt before the handler is fully registered,
or if devm_request_threaded_irq() fails entirely and returns without
subsequently masking the hardware interrupt, could this unhandled interrupt
trigger an IRQ storm? This might cause the kernel's irq core to permanently
disable the shared interrupt line.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260623-panthor-signal-from-irq-v3-0-2ece396f8ee0@collabora.com?part=3
next prev parent reply other threads:[~2026-06-23 13:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 12:51 [PATCH v3 0/7] drm/panthor: Reduce dma_fence signalling latency Boris Brezillon
2026-06-23 12:51 ` [PATCH v3 1/7] drm/panthor: Make panthor_irq::state a non-atomic field Boris Brezillon
2026-06-23 12:51 ` [PATCH v3 2/7] drm/panthor: Move the register accessors before the IRQ helpers Boris Brezillon
2026-06-23 12:51 ` [PATCH v3 3/7] drm/panthor: Replace the panthor_irq macro machinery by inline helpers Boris Brezillon
2026-06-23 13:02 ` sashiko-bot [this message]
2026-06-23 12:51 ` [PATCH v3 4/7] drm/panthor: Protect events processing with a separate spinlock Boris Brezillon
2026-06-23 13:07 ` sashiko-bot
2026-06-23 12:51 ` [PATCH v3 5/7] drm/panthor: Don't defer job completion checks Boris Brezillon
2026-06-23 12:51 ` [PATCH v3 6/7] drm/panthor: Don't defer FW event processing Boris Brezillon
2026-06-23 12:51 ` [PATCH v3 7/7] drm/panthor: Automate CSG IRQ processing at group unbind time Boris Brezillon
2026-06-23 13:04 ` sashiko-bot
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=20260623130232.862511F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.