-
Type:
Task
-
Resolution: Won't Fix
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Not Applicable
-
StorEng - 2023-08-08, ASeasonTooMany-2023-08-22, BermudaTriangle- 2023-09-05, TheMoon-StorEng - 2023-09-19, NachoCheese - 2023-10-03, Joker - StorEng - 2023-10-17, Asparagus-StorEng - 2023-10-31, c(3x10^8)-StorEng - 2023-11-14, 2023-11-28 - Anthill Tiger
-
5
There are three WT_ORDERED_READs in generations.c that have the comment: "Ensure we only read the value once.". The investigation in WT-11280 highlighted that these WT_ORDERED_READs effectively serve no purpose as they aren't enforcing ordering and the generation arrays are all volatile already.
The code wants READ_ONCE semantics and already has it but also chose to use ordered reads.
There are other places in the code where obvious volatile casts exist to achieve READ_ONCE, we should also convert those.
- is related to
-
WT-11280 Generation tracking might not be properly synchronized
-
- Closed
-