https://bugzilla.novell.com/show_bug.cgi?id=66013
https://bugzilla.novell.com/show_bug.cgi?id=66013#c7
Peter Morreale changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Group|SUSE Enterprise Partner |
Version|RC |Final
CC| |chrubis@novell.com,
| |jkosina@novell.com,
| |pmorreale@novell.com
Component|Kernel |Basesystem
Platform|i386 |x86-64
AssignedTo|andrea@novell.com |bnc-team-screening@forge.pr
| |ovo.novell.com
Resolution|WONTFIX |
Target Milestone|--- |Final
Product|SUSE LINUX 9.2 Professional |openSUSE 11.3
--- Comment #7 from Peter Morreale 2011-06-07 08:02:42 MDT ---
re-opening as the LTP test: .../pthread_rwlock_rdlock/2-1 clearly demonstrates
that the issue still exists in (at least) OS-11.3.
POSIX clearly states that if a writer is blocked, an additional reader entering
into the lock must block until the writer has released the lock.
pthread_rwlock_rdlock() does not implement that behavior. The additional
reader obtains the lock while a thread wanting the write mode is blocked.
The behavior of the 2-1 test is:
main thread: -> obtain read lock
writer thread: -> attempt to obtain write lock - block
reader tread: -> attempt to obtain read lock - succeeds.
The reader thread must block, since another thread wants a write lock.
There are, quite possibly, a lot of broken programs out there if they are
dependent upon documented behavior.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.