diff options
| author | Cong Nguyen <congnt264@gmail.com> | 2026-09-14 17:41:36 +0700 |
|---|---|---|
| committer | Guenter Roeck <linux@roeck-us.net> | 2026-09-14 08:24:55 -0700 |
| commit | bdf5f731957de48acada392f28e82bc019713adb (patch) | |
| tree | 0ba45dc2fe5e93e975209f0ba71f7ec2105b2d1c /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 06bd6794b5fd2163880ac3bfe973d4cc61f359f3 (diff) | |
| download | linux-next-bdf5f731957de48acada392f28e82bc019713adb.tar.gz linux-next-bdf5f731957de48acada392f28e82bc019713adb.zip | |
hwmon: (gpio-fan) return IRQ_HANDLED from the shared alarm IRQ handler
fan_alarm_irq_handler() always schedules alarm_work but returns IRQ_NONE,
so the kernel treats every alarm interrupt as unhandled. On a shared
line that risks the whole line being disabled as spurious.
v1 just fixed that, but it was still IRQF_SHARED, and always returning
IRQ_HANDLED there defeats spurious-interrupt detection for the line --
if the interrupt ever fires without a real event, nothing catches it,
and a fault could spin the CPU in the handler.
Sashiko flagged this in v1, and Guenter confirmed: this interrupt must
not be shared. So v2 drops IRQF_SHARED too.
Fixes: d6fe1360f42e ("hwmon: add generic GPIO fan driver")
Reported-by: Sashiko AI review <sashiko-bot@kernel.org>
Link: https://lore.kernel.org/r/20260901160931.DD3811F00A3D@smtp.kernel.org
Assisted-by: Claude:claude-opus-4
Signed-off-by: Cong Nguyen <congnt264@gmail.com>
Link: https://patch.msgid.link/20260914104136.1797979-1-congnt264@gmail.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
