Bug 176936 - NPTL: Thread scheduling and read-write locks.
Summary: NPTL: Thread scheduling and read-write locks.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: glibc
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
URL: http://nptl.bullopensource.org/Tests/...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-01-04 15:29 UTC by Tony Reix
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-01-04 17:11:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tony Reix 2006-01-04 15:29:33 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
OPTS test:

pthread_rwlock_rdlock/2-{1,2}.c
pthread_rwlock_unlock/3-1.c

These tests check several situations where POSIX specifies which thread shall acquire the lock.

The Linux / NPTL behavior does not obey the POSIX requirements about thread schedulin


Details are available at:
http://nptl.bullopensource.org/Tests/results/report.php
Browse: (TC2) 2xi686HT - RHAS4u2 Run 1,2,3

See:
http://nptl.bullopensource.org/Tests/results/detailed.php?run_id=12&testcase_id=1923
http://nptl.bullopensource.org/Tests/results/detailed.php?run_id=12&testcase_id=1925
http://nptl.bullopensource.org/Tests/results/detailed.php?run_id=12&testcase_id=2464

Version-Release number of selected component (if applicable):
Unmodified RHEL4u2

How reproducible:
Always

Steps to Reproduce:
Use OPTS.
(Used version was:  OPTS cvs repository on Nov 14, 2005)

Actual Results:  See:
http://nptl.bullopensource.org/Tests/results/detailed.php?run_id=12&testcase_id=1923
http://nptl.bullopensource.org/Tests/results/detailed.php?run_id=12&testcase_id=1925
http://nptl.bullopensource.org/Tests/results/detailed.php?run_id=12&testcase_id=2464

Additional info:

Comment 2 Tony Reix 2006-01-04 16:02:05 UTC
Use the 3 (correct !) URLS:

http://nptl.bullopensource.org/Tests/TC2/report.php#problems

http://nptl.bullopensource.org/Tests/results/run-browse.php
     Click the "Browse" button of : (TC2) 2xi686HT - RHAS4u2 Run 3
     You can also select 2 runs and click the "Compare Selected" button.


Comment 3 Ulrich Drepper 2006-01-04 17:11:42 UTC
There is no guarantee about the scheduling in this implementation.

Comment 4 Sebastien Decugis 2006-01-05 14:38:51 UTC
(In reply to comment #3)
> There is no guarantee about the scheduling in this implementation.

Therefore this *is* an issue, since POSIX has some requirements about
scheduling, and NPTL claims to implement this standard. Where is the mistake?


Note You need to log in before you can comment on or make changes to this bug.