BKL: Remove BKL from ecryptfs
The BKL is only used in fill_super, which is protected by the superblocks s_umount rw_semaphorei, and in fasync, which does not do anything that could require the BKL. Therefore it is safe to remove the BKL entirely. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Cc: Dustin Kirkland <kirkland@canonical.com> Cc: Tyler Hicks <tyhicks@linux.vnet.ibm.com> Cc: ecryptfs-devel@lists.launchpad.net
This commit is contained in:
@ -31,7 +31,6 @@
|
||||
#include <linux/security.h>
|
||||
#include <linux/compat.h>
|
||||
#include <linux/fs_stack.h>
|
||||
#include <linux/smp_lock.h>
|
||||
#include "ecryptfs_kernel.h"
|
||||
|
||||
/**
|
||||
@ -284,11 +283,9 @@ static int ecryptfs_fasync(int fd, struct file *file, int flag)
|
||||
int rc = 0;
|
||||
struct file *lower_file = NULL;
|
||||
|
||||
lock_kernel();
|
||||
lower_file = ecryptfs_file_to_lower(file);
|
||||
if (lower_file->f_op && lower_file->f_op->fasync)
|
||||
rc = lower_file->f_op->fasync(fd, lower_file, flag);
|
||||
unlock_kernel();
|
||||
return rc;
|
||||
}
|
||||
|
||||
|
Reference in New Issue
Block a user