| commit | a114a9d69d1362546b9dda651028acb311ddb7af | |
| author | Christian Borntraeger <borntraeger@de.ibm.com> | |
| Thu, 25 Dec 2008 12:38:34 +0000 (25 13:38 +0100) | ||
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | |
| Thu, 25 Dec 2008 12:38:54 +0000 (25 13:38 +0100) | ||
| tree | c538cbdb79ca97bd06d889d62300f0fbf53c3c6a | treesnapshot (tar.gz zip) |
| parent | f414f5f15376764d68a31dc568d9e814d3fcb58a | commitdiff |
[S390] vmcp: remove BKL
The vmcp driver uses the session->mutex for concurrent access of the data
structures. Therefore, the BKL in vmcp_open does not protect against any
other function in the driver.
The BLK in vmcp_open would protect concurrent access to the module init
but all necessary steps ave finished before misc_register is called.
We can safely remove the lock_kernel from vcmp.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
The vmcp driver uses the session->mutex for concurrent access of the data
structures. Therefore, the BKL in vmcp_open does not protect against any
other function in the driver.
The BLK in vmcp_open would protect concurrent access to the module init
but all necessary steps ave finished before misc_register is called.
We can safely remove the lock_kernel from vcmp.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
| drivers/s390/char/vmcp.c | diffblobblamehistory |