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:
@ -898,7 +898,6 @@ static int sonypi_misc_fasync(int fd, struct file *filp, int on)
|
||||
|
||||
static int sonypi_misc_release(struct inode *inode, struct file *file)
|
||||
{
|
||||
sonypi_misc_fasync(-1, file, 0);
|
||||
mutex_lock(&sonypi_device.lock);
|
||||
sonypi_device.open_count--;
|
||||
mutex_unlock(&sonypi_device.lock);
|
||||
|
Reference in New Issue
Block a user