ibm-information-center/dist/eclipse/plugins/i5OS.ic.apis_5.4.0.1/users_65.htm

247 lines
7.8 KiB
HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
<title>pthread_mutex_unlock()--Unlock Mutex</title>
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<!-- Begin Header Records ========================================== -->
<!-- NETMG2 SCRIPT A converted by B2H R4.1 (346) (CMS) by HOLTJM at -->
<!-- RCHVMW2 on 29 Jan 1999 at 10:01:37 -->
<!--File Edited November 2001 -->
<!--End Header Records -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<!-- Java sync-link -->
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript">
</script>
<a name="Top_Of_Page"></a>
<h2>pthread_mutex_unlock()--Unlock Mutex</h2>
<div class="box" style="width: 60%;">
<br>
&nbsp;&nbsp;Syntax:
<pre>
#include &lt;pthread.h&gt;
int pthread_mutex_unlock(pthread_mutex_t *mutex);
</pre>
&nbsp;&nbsp;Service Program Name: QP0WPTHR<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Default Public Authority: *USE<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Threadsafe: Yes<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Signal Safe: Yes<br>
<!-- iddvc RMBR -->
<br>
</div>
<p>The <strong>pthread_mutex_unlock</strong>() function unlocks the mutex
specified. If the calling thread does not currently hold the mutex (via a
previous call to <strong>pthread_mutex_lock</strong>(),
<strong>pthread_mutex_trylock</strong>(), or <strong>
pthread_mutex_timedlock_np</strong>()) the unlock request fails with the
<strong>EPERM</strong> error.</p>
<p>Mutex initialization using the <strong>PTHREAD_MUTEX_INITIALIZER</strong>
does not immediately initialize the mutex. Instead, on first use,
<strong>pthread_mutex_timedlock_np</strong>() or
<strong>pthread_mutex_lock</strong>() or
<strong>pthread_mutex_trylock</strong>() branches into a slow path and causes
the initialization of the mutex. Because a mutex is not just a simple memory
object and requires that some resources be allocated by the system, an attempt
to call <strong>pthread_mutex_destroy</strong>() or
<strong>pthread_mutex_unlock</strong>() on a mutex that was statically
initialized using <strong>PTHREAD_MUTEX_INITIALIZER</strong> and was not yet
locked causes an <strong>EINVAL</strong> error.</p>
<br>
<h3>Mutex Types</h3>
<p>A normal mutex cannot be locked repeatedly by the owner. Attempts by a
thread to relock an already held mutex, or to lock a mutex that was held by
another thread when that thread terminated, cause a deadlock condition.</p>
<p>A recursive mutex can be locked repeatedly by the owner. The mutex does not
become unlocked until the owner has called
<strong>pthread_mutex_unlock</strong>() for each successful lock request that
it has outstanding on the mutex.</p>
<p>An errorcheck mutex checks for deadlock conditions that occur when a thread
relocks an already held mutex. If a thread attempts to relock a mutex that it
already holds, the lock request fails with the <strong>EDEADLK</strong>
error.</p>
<p>An ownerterm mutex is an i5/OS extension to the errorcheck mutex type. An
ownerterm mutex checks for deadlock conditions that occur when a thread relocks
an already held mutex. If a thread attempts to relock a mutex that it already
holds, the lock request fails with the <strong>EDEADLK</strong> error. An
ownerterm mutex also checks for deadlock conditions that occur when a thread
attempts to lock a mutex that was held by another thread when that thread
terminated (an orphaned mutex). If a thread attempts to lock an orphaned mutex,
the lock request fails with the <strong>EOWNERTERM</strong> error.</p>
<p>When a thread terminates while holding a mutex lock on a normal or
errorcheck mutex, other threads that wait for that mutex will block forever.
The pthreads run-time simulates the deadlock that has occurred in your
application. When you are attempting to debug these deadlock scenarios, the CL
command WRKJOB, option 20, shows the thread as in a condition wait. Displaying
the call stack shows that the function
<strong>deadlockOnOrphanedMutex</strong> is in the call stack.</p>
<p>When a thread attempts to acquire a normal mutex that it already holds, the
thread will block forever. The pthreads run-time simulates the deadlock that
has occurred in your application. When you are attempting to debug these
deadlock scenarios, the CL command WRKJOB, option 20, shows the thread as in a
condition wait. Displaying the call stack shows that the function
<strong>deadlockOnAlreadyHeldMutex</strong> is in the call stack.</p>
<p>To change these behaviors, use an errorcheck or ownerterm mutex type.</p>
<br>
<h3>Authorities and Locks</h3>
<p>For successful completion, the mutex lock must be held before you call
<strong>pthread_mutex_unlock</strong>().</p>
<br>
<h3>Parameters</h3>
<dl>
<dt><strong>mutex</strong></dt>
<dd>(Input) Address of the mutex to unlock</dd>
</dl>
<br>
<h3>Return Value</h3>
<dl>
<dt><strong>0</strong></dt>
<dd><strong>pthread_mutex_unlock</strong>() was successful.</dd>
<dt><strong>value</strong></dt>
<dd><strong>pthread_mutex_unlock</strong>() was not successful. <em>value</em>
is set to indicate the error condition.</dd>
</dl>
<br>
<h3>Error Conditions</h3>
<p>If <strong>pthread_mutex_unlock</strong>() was not successful, the error
condition returned usually indicates one of the following errors. Under some
conditions, the value returned could indicate an error other than those listed
here.</p>
<dl>
<dt><em>[EINVAL]</em></dt>
<dd>
<p>The value specified for the argument is not correct.</p>
</dd>
<dt><em>[EPERM]</em></dt>
<dd>
<p>The mutex is not currently held by the caller.</p>
</dd>
</dl>
<br>
<h3>Related Information</h3>
<ul>
<li>The &lt;<strong>pthread.h</strong>&gt; header file. See <a href=
"rzah4hed.htm">Header files for Pthread functions</a>.<br><br></li>
<li><a href="users_60.htm">pthread_mutex_destroy()</a>--Destroy Mutex<br><br></li>
<li><a href="users_61.htm">pthread_mutex_init()</a>--Initialize Mutex<br><br></li>
<li><a href="users_62.htm">pthread_mutex_lock()</a>--Lock Mutex<br><br></li>
<li><a href="users_63.htm">pthread_mutex_timedlock_np()</a>--Lock Mutex with Time-Out<br><br></li>
<li><a href="users_64.htm">pthread_mutex_trylock()</a>--Lock Mutex with No
Wait</li>
</ul>
<br>
<h3>Example</h3>
<p>See <a href="../apiref/aboutapis.htm#codedisclaimer">Code disclaimer information</a>
for information pertaining to code examples.</p>
<pre>
#include &lt;pthread.h&gt;
#include &lt;stdio.h&gt;
#include "check.h"
pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER;
int main(int argc, char **argv)
{
int rc=0;
printf("Entering testcase\n");
printf("Lock the mutex\n");
rc = pthread_mutex_lock(&amp;mutex);
checkResults("pthread_mutex_lock()\n", rc);
/* All other threads will be blocked from the resource here */
printf("Unlock the mutex\n");
rc = pthread_mutex_unlock(&amp;mutex);
checkResults("pthread_mutex_unlock()\n", rc);
printf("Destroy the mutex\n");
rc = pthread_mutex_destroy(&amp;mutex);
checkResults("pthread_mutex_destroy()\n", rc);
printf("Main completed\n");
return 0;
}
</pre>
<p><strong>Output:</strong></p>
<pre>
Entering testcase
Lock the mutex
Unlock the mutex
Destroy the mutex
Main completed
</pre>
<hr>
API introduced: V4R3
<hr>
<center>
<table cellpadding="2" cellspacing="2">
<tr align="center">
<td valign="middle" align="center"><a href="#Top_Of_Page">Top</a> | <a href=
"rzah4mst.htm">Pthread APIs</a> | <a href="aplist.htm">APIs by
category</a></td>
</tr>
</table>
</center>
</body>
</html>