-
Type:
Epic
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Engines - Foundations
-
103.072
-
None
-
None
-
Resolve known WT TSAN warnings
Description
Fix the WT warnings already reported by TSAN, including warnings that were suppressed during rollout. Reduce the suppression list gradually, and make it clear why each remaining exception exists.
Current suppression list
The 13 November 2026 source snapshot contains 75 runtime entries, 74 distinct patterns, and 68 source lines containing suppression-helper calls/macros outside the helper definitions. These are inventory counts, not counts of distinct bugs.
The runtime entries include ticketed warning groups for reconfigure, backup/examples, allocation/access, TAILQ, Python, performance-sensitive code, statistics logging, timestamps, and prepare-state handling. Format-harness warnings belong with the testing-gap work rather than production-warning fixes.
Three column-store patterns have no ticket reference in their source block: __wt_col_modify, __inmem_col_var, __wt_col_search.
Eight other production patterns have no ticket reference in their source block: __wt_cell_type, __posix_file_read, __wt_cell_unpack_safe, __cursor_var_next, __cursor_var_prev, __tombstone_update_alloc, __wt_btcur_modify, __wt_cursor_dhandle_decr_use.
Explained exceptions without per-entry ticket keys include statistics, helper functions, diagnostic tracking, SQLite WAL functions, deferred checkpoint queries, and method configuration. Their comments are evidence to review, not certification that the suppressions are justified.
Unticketed patterns may overlap existing umbrellas. Do not create assumed-defect tickets from pattern names. Match them to existing reports or reproduce the warnings first.
TBD — gradual suppression reduction
Create small tickets for reducing the suppression list, grouped by existing warning/ticket and owning subsystem:
- Match unticketed patterns and helper sites to existing reports; reproduce cases where evidence is missing.
- Pick a manageable warning group, fix it or document why it remains suppressed, and remove/narrow the corresponding suppression.
- Review broad file/function/wildcard entries and stale entries gradually, rather than replacing the backlog with another large umbrella.
- Identify missing focused tickets only after checking for duplicates and TSAN evidence.
Ticket grouping, order, owners, and milestones are TBD. These are work to scope, not finalized new ticket drafts.
TBD — how every exception is documented
Agree a short set of rules for every exception. The explanation should live next to the exception: a code comment for a helper/annotation/TSAN-specific path, or a comment immediately above the suppression-file entry/group.
Proposed information, subject to review:
- What warning is suppressed and where its report/reproduction is recorded.
- Why it is suppressed: a known issue awaiting a fix, a sanitizer limitation, or another explicit reason—not just "TSAN warning".
- Which ticket owns the fix or investigation, where applicable.
- Enough scope information to explain a broad suppression and when it can be removed.
- A short recorded justification for an exception intended to remain without a fix ticket.
The exact comment format, treatment of shared patterns, and automated checks are TBD. An exception without an explanation should be flagged for review, not automatically treated as acceptable.
- related to
-
WT-19085 Enable WT TSAN testing through MongoDB tests
-
- Open
-