Open Bug 1067760 Opened 12 years ago Updated 2 years ago

Reading |rwlock->rw_owner| without lock in NSSRWLock_HaveWriteLock() might be not safe

Categories

(NSS :: Libraries, defect, P3)

Tracking

(Not tracked)

People

(Reporter: jwwang, Unassigned)

Details

See bug 1067414 comment 3. Compiler optimization is free to spill a temp value into |rwlock->rw_owner|. Even if read/write to |rwlock->rw_owner| takes only one instruction, it is still possible to see a value other than any of thread IDs in |rwlock->rw_owner| when compiler doing crazy optimization.
Severity: normal → S3
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.