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] [day] [month] [year] [list]
Date:	Sat, 14 Jan 2012 15:53:55 +0800
From:	Cong Wang <xiyou.wangcong@...il.com>
To:	Feng Ye <f_ye@...oo.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: How to wait for threaded irq handler to finish, as in work queue
 flush/cancel?

On 01/14/2012 01:40 PM, Feng Ye wrote:
> Hello there,
>
>
> I have a question regarding how to cancel threaded irq handler in a driver's suspend function.
> If it's NOT threaded irq, normally you have a work queue, and in the suspend function, you call either cancel_work_sync() or flush_work(), these function will WAIT for the work queue to finish if it's in the middle of something.
> However if you use threaded irq, then you don't need a work queue, then in the suspend function, I don't know if there's a simple function that can be used to cancel and wait the thread to finish?
>
>

Hi,

Isn't free_irq() what you want?

/**
  *      free_irq - free an interrupt allocated with request_irq
  *      @irq: Interrupt line to free
  *      @dev_id: Device identity to free
  *
  *      Remove an interrupt handler. The handler is removed and if the
  *      interrupt line is no longer in use by any driver it is disabled.
  *      On a shared IRQ the caller must ensure the interrupt is disabled
  *      on the card it drives before calling this function. The function
  *      does not return until any executing interrupts for this IRQ
  *      have completed.
  *
  *      This function must not be called from interrupt context.
  */

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