mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Cong Nguyen <congnt264@gmail.com>
Cc: Simon Guinot <sguinot@lacie.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] hwmon: (gpio-fan) return IRQ_HANDLED from the shared alarm IRQ handler
Date: Mon, 14 Sep 2026 08:25:23 -0700	[thread overview]
Message-ID: <53810ee8-8b5c-41ed-8644-ba23fd69bb81@roeck-us.net> (raw)
In-Reply-To: <20260914104136.1797979-1-congnt264@gmail.com>

On Mon, Sep 14, 2026 at 05:41:36PM +0700, Cong Nguyen wrote:
> 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>

Applied.

Thanks,
Guenter

      reply	other threads:[~2026-09-14 15:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 10:41 Cong Nguyen
2026-09-14 15:25 ` Guenter Roeck [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=53810ee8-8b5c-41ed-8644-ba23fd69bb81@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=congnt264@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sguinot@lacie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®