From c6556e2ecc6b80f981bb210d541544f24b7f59df Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Wed, 1 Jun 2016 14:38:05 +0200 Subject: score: Maybe fix _Thread_Lock_acquire() The approach with the generation number was broken. The load/store of the current lock, the thread queue and the thread queue operations were not properly synchronized. Under certain conditions on a PowerPC T4240 old thread queue operations operated on a new thread queue (NULL pointer). --- cpukit/score/include/rtems/score/thread.h | 5 ----- 1 file changed, 5 deletions(-) (limited to 'cpukit/score/include/rtems/score/thread.h') diff --git a/cpukit/score/include/rtems/score/thread.h b/cpukit/score/include/rtems/score/thread.h index 4618a409eb..7491e8fcdf 100644 --- a/cpukit/score/include/rtems/score/thread.h +++ b/cpukit/score/include/rtems/score/thread.h @@ -691,11 +691,6 @@ typedef struct { */ SMP_lock_Stats Stats; #endif - - /** - * @brief Generation number to invalidate stale locks. - */ - Atomic_Uint generation; } Thread_Lock_control; #endif -- cgit v1.2.3