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:
@@ -1070,8 +1070,6 @@ static int tun_chr_close(struct inode *inode, struct file *file)
|
||||
|
||||
DBG(KERN_INFO "%s: tun_chr_close\n", tun->dev->name);
|
||||
|
||||
tun_chr_fasync(-1, file, 0);
|
||||
|
||||
rtnl_lock();
|
||||
|
||||
/* Detach from net device */
|
||||
|
Reference in New Issue
Block a user