Linux-kernel mailing list archive 2000-01,: release not called for my driver?

# release not called for my driver?

Stephen Williams (steve@icarus.com)
Mon, 03 Jan 2000 11:20:32 -0800

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Mike Sensney: "Re: 2.2.14pre17,pre18: lock up possibly related to floppy"
- Previous message: Theodore Y. Ts'o: "Re: Unexecutable Stack / Buffer Overflow Exploits..."
- Next in thread: Alan Cox: "Re: release not called for my driver?"
- Reply: Alan Cox: "Re: release not called for my driver?"

I have a driver for an image processing board that I ported from 2.0 to
2.2 kernels. (I did the port a while ago, actually.) It basically works,
but I'm having some trouble with the release function not being called.

The driver supports mmap, as well as open/close/read/write. When I open
the driver, do reads and writes, and kill the application that opened
the device, I get the call to release exactly how I expect. HOwever, if
the application does a mmap of the device, then killing the device will
cause the vmclose to be called, BUT RELEASE IS NOT CALLED.

This driver has been working great under 2.0 for some time, and other then
this problem, seems to work fine under 2.2. I believe it also worked
properly under 2.1 kernels, so I don't know when my problem started.

So what am I doing wrong? What can cause this?

Linux/Intel 2.2.13 kernel, although I generally support alpha as well.

    --
    Steve Williams                "The woods are lovely, dark and deep.
    steve@icarus.com              But I have promises to keep,
    steve@picturel.com            and lines to code before I sleep,
    http://www.picturel.com       And lines to code before I sleep."

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.rutgers.edu
    Please read the FAQ at http://www.tux.org/lkml/

- Next message: Mike Sensney: "Re: 2.2.14pre17,pre18: lock up possibly related to floppy"
- Previous message: Theodore Y. Ts'o: "Re: Unexecutable Stack / Buffer Overflow Exploits..."
- Next in thread: Alan Cox: "Re: release not called for my driver?"
- Reply: Alan Cox: "Re: release not called for my driver?"