- --- Forwarded Message
To: Andi Kleen <[EMAIL PROTECTED]>
Subject: Re: kernel threads and close method in a device driver
In-Reply-To: Your message of "Tue, 17 Apr 2001 23:43:39 +0200."
<[EMAIL PROTECTED]>
Date: Wed, 18 Apr 2001 10:49:04 -0400
From: "Marty
- --- Forwarded Message
To: Andi Kleen [EMAIL PROTECTED]
Subject: Re: kernel threads and close method in a device driver
In-Reply-To: Your message of "Tue, 17 Apr 2001 23:43:39 +0200."
[EMAIL PROTECTED]
Date: Wed, 18 Apr 2001 10:49:04 -0400
From: "Marty Leisner&qu
[EMAIL PROTECTED] said:
> The architecture is currently:
> open device
> do IOCTL (spinning a kernel thread and doing initialization)
> There is currently an IOCTL which short-circuits to the close method.
> Turns out it seems necessary to do this IOCTL -- close never gets
> invoked.
> What can cause a close not to get invoked? BTW, the close is returning
> with a 0 status to the application ...(it definitely did NOT
> get invoked in the driver)
The driver release function is invoked when the use count of the handle hits
zero. Make sure you are not muddling release and
On Tue, Apr 17, 2001 at 05:04:28PM -0400, Marty Leisner wrote:
> open device
> do IOCTL (spinning a kernel thread and doing initialization)
>
> There is currently an IOCTL which short-circuits to the close method.
> Turns out it seems necessary to do this IOCTL -- close never gets
>
I'm involved with modifying a device driver for new hardware.
The architecture is currently:
open device
do IOCTL (spinning a kernel thread and doing initialization)
There is currently an IOCTL which short-circuits to the close method.
Turns out it seems necessary to do this
I'm involved with modifying a device driver for new hardware.
The architecture is currently:
open device
do IOCTL (spinning a kernel thread and doing initialization)
There is currently an IOCTL which short-circuits to the close method.
Turns out it seems necessary to do this
On Tue, Apr 17, 2001 at 05:04:28PM -0400, Marty Leisner wrote:
open device
do IOCTL (spinning a kernel thread and doing initialization)
There is currently an IOCTL which short-circuits to the close method.
Turns out it seems necessary to do this IOCTL -- close never gets
What can cause a close not to get invoked? BTW, the close is returning
with a 0 status to the application ...(it definitely did NOT
get invoked in the driver)
The driver release function is invoked when the use count of the handle hits
zero. Make sure you are not muddling release and flush
[EMAIL PROTECTED] said:
The architecture is currently:
open device
do IOCTL (spinning a kernel thread and doing initialization)
There is currently an IOCTL which short-circuits to the close method.
Turns out it seems necessary to do this IOCTL -- close never gets
invoked.
10 matches
Mail list logo