linux-kernel - Re: Using "Asynchronous Notifications" within an interrupt handler

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: <Pine.LNX.4.61.0610060741040.12702@yvahk01.tjqt.qr>
Date:	Fri, 6 Oct 2006 07:42:22 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Madhu Saravana Sibi Govindan <ssshayagriva@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Using "Asynchronous Notifications" within an interrupt handler

>
> 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?

It may be possible - I have an old driver for custom hardware lying 
around here, and it does this in the irq handler:

kill_fasync(&global.fasync_ptr, SIGIO, POLL_IN);



	-`J'
-- 
-
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/