mirror of
https://github.com/Fishwaldo/linux-bl808.git
synced 2025-06-17 20:25:19 +00:00
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
1 changed files with 1 additions and 1 deletions
|
@ -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? */
|
/* do we really need this? can a write happen after a close? */
|
||||||
if ((kbuf->cmd == DLM_USER_LOCK || kbuf->cmd == DLM_USER_UNLOCK) &&
|
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;
|
return -EINVAL;
|
||||||
|
|
||||||
sigfillset(&allsigs);
|
sigfillset(&allsigs);
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue