linux-kernel - threaded irq handler thread doesn't run

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:	Sun, 1 Nov 2009 14:05:44 +0100
From:	Manuel Lauss <manuel.lauss@...glemail.com>
To:	linux-kernel@...r.kernel.org
Subject: threaded irq handler thread doesn't run

Hello!

I noticed that the thread of a threaded irq doesn't run if the interrupt
is disabled:  I have a semi-broken system with 2 carddetect interrupts,
both are supposed to be edge-triggered, but due to broken PLD they
continue screaming as long as their trigger condition is met.  To work
around this, the triggering one is disabled while the other gets enabled;
disabling occurs in the "fast" handler, enabling in the threaded handler:

static irqreturn_t threadfn(irq, ctx)
{
    ...
      enable_irq(irq == cd1int ? cd2int : cd1int);
    ...
}

static irqreturn_t fastint(irq, ctx)
{
  disable_irq_nosync(irq);
  return IRQ_WAKE_THREAD;
}
...
request_threaded_irq(cd1int, fastint, threadfn, 0, "insert", ctx);
request_threaded_irq(cd2int, fastint, threadfn, 0, "eject", ctx);

In kernel/irq/manage.c::irq_thread(), the thread func isn't run
if the irq has been disabled; is there a way around this?
(removing that restriction completely solves it for me, but I
doubt this is acceptable for others).

Thanks!
     Manuel Lauss
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/