Hi,
On Tue, Feb 19, Rusty Russell wrote:
> This means we need a move the "struct fasync_struct
> fasync_list" into struct file (up from all the subsystems which use
> it, eg. struct socket).
>
> See any problems with this?
At first I thought I would clean up the drivers a little moving common
code from the release routine. The release code is not called in the
example you gave because of the fork, correct ?
Then I realised what happens if several processes all request SIGIO
notification on different descriptors. The driver still needs to keep
a private list of all the processes registered with it. struct file
should at best contain a pointer back to the relevant structure in the
driver private list for cleanup ?
--
Bob Dunlop
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Feb 23 2002 - 21:00:18 EST