Since the reader can always acquire the rwlock if there's not a writer held the lock.
Signed-off-by: Wanlong Gao <[email protected]> --- .../conformance/interfaces/pthread_rwlock_rdlock/2-1.c | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/testcases/open_posix_testsuite/conformance/interfaces/pthread_rwlock_rdlock/2-1.c b/testcases/open_posix_testsuite/conformance/interfaces/pthread_rwlock_rdlock/2-1.c index c6c1412..62a4b3b 100644 --- a/testcases/open_posix_testsuite/conformance/interfaces/pthread_rwlock_rdlock/2-1.c +++ b/testcases/open_posix_testsuite/conformance/interfaces/pthread_rwlock_rdlock/2-1.c @@ -141,6 +141,12 @@ int main(void) return PTS_UNSUPPORTED; #endif +#ifdef __GLIBC__ + printf("The reader can always acquire rwlock if there's" + " not a writer held this lock in glibc\n"); + return PTS_UNTESTED; +#endif + int cnt = 0; pthread_t rd_thread, wr_thread; int priority; -- 1.8.3.3.754.g9c3c367 ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
