Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-2139

LSM with read-uncommitted isolation, read after free

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • WT2.7.0, 3.0.13
    • Affects Version/s: None
    • Component/s: None
    • None

      michael.cahill says:

      To clarify, what I was trying to say is that we have seen various failures when running LSM with read-uncommitted isolation that suggest that the oldest transaction ID is not being pinned correctly during a read. That has been detected as read-after-free by address sanitizer, and I guess could conceivably lead to memory corruption, though I can't see a direct path that explains this bug.

            Assignee:
            Unassigned Unassigned
            Reporter:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: