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:
@@ -264,8 +264,11 @@ static int snd_disconnect_release(struct inode *inode, struct file *file)
|
||||
}
|
||||
spin_unlock(&shutdown_lock);
|
||||
|
||||
if (likely(df))
|
||||
if (likely(df)) {
|
||||
if ((file->f_flags & FASYNC) && df->disconnected_f_op->fasync)
|
||||
df->disconnected_f_op->fasync(-1, file, 0);
|
||||
return df->disconnected_f_op->release(inode, file);
|
||||
}
|
||||
|
||||
panic("%s(%p, %p) failed!", __func__, inode, file);
|
||||
}
|
||||
|
Reference in New Issue
Block a user