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-next>] [day] [month] [year] [list]
Date:	Thu, 5 Oct 2006 19:53:02 -0500
From:	"Madhu Saravana Sibi Govindan" <ssshayagriva@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Using "Asynchronous Notifications" within an interrupt handler

Hello all,

I'm developing a linux device driver for kernel version 2.16.15. I'm
thinking of using the "Asynchronous Notification" mechanism, explained
in the Linux Device Drivers book by Corbet and Rubini in Chapter 6,
within an interrupt handler.

The idea is: whenever the device driver receives an interrupt from the
hardware device, the interrupt handler uses this 'asynchronous
notification' mechanism to notify a user-level process of this
interrupt. The user-level process, on the other hand, is waiting for
this SIGIO signal from the device driver.

My question is: is it safe to use the asynchronous notification
mechanism within an interrupt handler? I see that this call acquires a
bunch of locks before sending the signal to the process. Would this
cause any deadlocking situations? Or should I resort to the top and
bottom half approach for interrupt handling and handle the
notification in the bottom half?

I'd be very thankful for suggestions/ideas on this topic.

Regards and thanks in advance,
G.Sibi

PS: I've posted this to os_drivers@...ts.osdl.org too. My apologies
for the duplication.
-
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