dlm: check for null in device_write
If `device_write' method is called via "dlm-control", file->private_data is NULL. (See ctl_device_open() in user.c. ) Through proc->flags is read. Signed-off-by: Masatake YAMATO <yamato@redhat.com> Signed-off-by: David Teigland <teigland@redhat.com>
This commit is contained in:
parent
bce7f793da
commit
254ae43ab8
@ -538,7 +538,7 @@ static ssize_t device_write(struct file *file, const char __user *buf,
|
||||
|
||||
/* do we really need this? can a write happen after a close? */
|
||||
if ((kbuf->cmd == DLM_USER_LOCK || kbuf->cmd == DLM_USER_UNLOCK) &&
|
||||
test_bit(DLM_PROC_FLAGS_CLOSING, &proc->flags))
|
||||
(proc && test_bit(DLM_PROC_FLAGS_CLOSING, &proc->flags)))
|
||||
return -EINVAL;
|
||||
|
||||
sigfillset(&allsigs);
|
||||
|
Loading…
Reference in New Issue
Block a user