[Bug 7750] open/close loop causes disabled irq (fwd)

[Alan Stern]

Alan:

Can this be ignored, or is it a case of a patch papering over a real
problem?  It seems possible that some serial driver is leaving device
IRQs enabled after it has unregistered itself as an interrupt handler.

Alan Stern


---------- Forwarded message ----------
Date: Thu, 12 Jul 2007 20:02:25 -0700 (PDT)
From: bugme-daemon@xxxxxxxxxxxxxxxxxxx
To: stern@xxxxxxxxxxxxxxxxxxx
Subject: [Bug 7750] open/close loop causes disabled irq

http://bugzilla.kernel.org/show_bug.cgi?id=7750





------- Comment #4 from dannf@xxxxxxxxx  2007-07-12 20:07 -------
I attempted to reproduce this today under 2.6.22 and was unable to. I then used
git bisect to try and identify the changeset that fixed the issue and ended up
with the one below.

I wonder if this should be considered a security issue (DoS)?

commit 8528b0f1de1101c6002036fd53638fb21111d0ea
Author: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Date:   Tue Jan 23 14:16:31 2007 -0800

    Clear spurious irq stat information when adding irq handler

    Any newly added irq handler may obviously make any old spurious irq
    status invalid, since the new handler may well be the thing that is
    supposed to handle any interrupts that came in.

    So just clear the statistics when adding handlers.

    Pointed-out-by: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
    Acked-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
    Acked-by: Ingo Molnar <mingo@xxxxxxx>
    Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>

:040000 040000 d3bd3ddf15462bca9f796e899b96f2e17d30bc34
3ea41ebe53747377873202db8b59e2c4e84aef8c M      kernel


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


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