This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug nptl/17561] GLIBC 2.20 results in SIGILL on x86_64 with double pthread_rwlock_unlock()


https://sourceware.org/bugzilla/show_bug.cgi?id=17561

Andrey Zabolotnyi <zapparello at ya dot ru> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |zapparello at ya dot ru

--- Comment #4 from Andrey Zabolotnyi <zapparello at ya dot ru> ---
Manual page for pthread_rwlock_unlock says:

[...]If an implementation detects that the value specified  by  the  rwlock 
argument  to  pthread_rwlock_unlock() refers  to a read-write lock object for
which the current thread does not hold a lock, it is recommended that the
function should fail and report an [EPERM] error.

So at least the current implementation does not follow the standard
recommendation.

Same applies for pthread_rwlock_rdlock() and then twice calling
pthread_rwlock_unlock() - program will SIGSEGV (in my case).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]