Messages in this thread | | | Subject | Re: Moving fasync_struct into struct file? | Date | Tue, 19 Feb 2002 09:11:48 +0000 (GMT) | From | Alan Cox <> |
| |
> the SIGIO. IMVHO the best way to clean this up is to check the > fasync_list in sys_close, and if pid == filp->f_owner.pid and fd == > fasync_list->fa_fd, unregister the SIGIO.
We already clean up fasync structures on close, its the drivers responsibility to do so. If you wanted to be more strict you could do a similar helper call in the other closing callback for each fd close.
> 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).
Any reason for not just caching the 32bit task ident field ? Using the slightly confusingly p->parent_exec_id, which is basically a 32bit process ident for example - 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/
| |