saner FASYNC handling on file close
As it is, all instances of ->release() for files that have ->fasync() need to remember to evict file from fasync lists; forgetting that creates a hole and we actually have a bunch that *does* forget. So let's keep our lives simple - let __fput() check FASYNC in file->f_flags and call ->fasync() there if it's been set. And lose that crap in ->release() instances - leaving it there is still valid, but we don't have to bother anymore. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
@ -990,7 +990,6 @@ static int sock_close(struct inode *inode, struct file *filp)
|
||||
printk(KERN_DEBUG "sock_close: NULL inode\n");
|
||||
return 0;
|
||||
}
|
||||
sock_fasync(-1, filp, 0);
|
||||
sock_release(SOCKET_I(inode));
|
||||
return 0;
|
||||
}
|
||||
|
Reference in New Issue
Block a user