Skip to contentSkip to conversation

locking problem with __cpcmd.

S390 Martin Schwidefsky 1 participant 1 message Jan 9, 2007 s390

lore
Share & tools
lore
#0 lore raw

From: Christian Borntraeger <[email protected]>

[S390] locking problem with __cpcmd.

Changeset 740b5706b9c4b3767f597b3ea76654c6f2a800b2 moved the protecting spinlock from __cpcmd to cpcmd. Therefore vmcp can no longer use __cpcmd, instead we have to use cpcmd.

---

 drivers/s390/char/vmcp.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)
drivers/s390/char/vmcp.c +1 -1
diff -urpN linux-2.6/drivers/s390/char/vmcp.c linux-2.6-patched/drivers/s390/char/vmcp.c
@@ -117,7 +117,7 @@ vmcp_write(struct file *file, const char
 		return -ENOMEM;
 	}
 	debug_text_event(vmcp_debug, 1, cmd);
-	session->resp_size = __cpcmd(cmd, session->response,
+	session->resp_size = cpcmd(cmd, session->response,
 				     session->bufsize,
 				     &session->resp_code);
 	up(&session->mutex);