[PATCH] btrfs: Don't check for file->private_data on open(). It is set by the core.

From: Martin Kepplinger
Date: Wed Nov 12 2014 - 11:40:39 EST


The miscdevice core now sets file->private_data to the struct miscdevice
so don't fail when this is not NULL.

Signed-off-by: Martin Kepplinger <martink@xxxxxxxxx>
---
This is a question: what does this check provide and does overwriting
file->private_data make any difference?

Is miscdevice's open() by the user not allowed here, if file->private_data
is set?

thanks!!

fs/btrfs/ioctl.c | 4 ----
1 file changed, 4 deletions(-)

diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
index 4399f0c..066ce41 100644
--- a/fs/btrfs/ioctl.c
+++ b/fs/btrfs/ioctl.c
@@ -3752,10 +3752,6 @@ static long btrfs_ioctl_trans_start(struct file *file)
if (!capable(CAP_SYS_ADMIN))
goto out;

- ret = -EINPROGRESS;
- if (file->private_data)
- goto out;
-
ret = -EROFS;
if (btrfs_root_readonly(root))
goto out;
--
1.7.10.4

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/