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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49A48C38.20209@gmail.com>
Date:	Tue, 24 Feb 2009 18:09:28 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Mike Mason <mmlnx@...ibm.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Disabling an interrupt in interrupt context

Mike Mason wrote:
> I have a need to disable an LSI interrupt from within the context of the 
> handler for that interrupt.  It appears that disable_irq_nosync() will 
> do the trick.  Besides dropping interrupts, which I don't care about 
> because the device is in an error state, what are the potential side 
> effects of doing this?  As far as I can tell, this will not prevent the 
> current in-flight handlers for that interrupt from finishing.

Well, if any other devices are sharing that IRQ line, they likely won't 
like it, for one thing.. How long are you planning on disabling the IRQ 
line for?
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ