Date: Wed, 31 Dec 2003 07:54:48 -0800 (PST) From: Mike Makonnen <mtm@FreeBSD.org> To: projects-committers@FreeBSD.org, cvs-projects@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: projects/validate/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_timedlock 5-1.c 5-2.c 5-3.c Message-ID: <200312311554.hBVFsmTp022013@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
mtm 2003/12/31 07:54:48 PST
FreeBSD projects repository
Modified files:
validate/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_timedlock
5-1.c
5-2.c
5-3.c
Log:
Correct incorrect assertion about the behaviour of pthread_mutex_timedlock()
o If the thread has the mutex already locked it will not block. It
will return EDEADLK. Therefore, according to the standard,
returning EINVAL if the timeout is invalid does not apply to
such a thread.
Better explanation for the case testing for immediate return
with ETIMEDOUT when the timeout is set to the current time.
Revision Changes Path
1.2 +25 -25 projects/validate/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_timedlock/5-1.c
1.2 +25 -26 projects/validate/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_timedlock/5-2.c
1.2 +4 -5 projects/validate/testcases/open_posix_testsuite/conformance/interfaces/pthread_mutex_timedlock/5-3.c
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312311554.hBVFsmTp022013>