[Bug 3903] New: Ancient glibc + parallel updates can cause manifest corruption during rebases

[mercurial-bugs at selenic.com]

http://bz.selenic.com/show_bug.cgi?id=3903

          Priority: normal
            Bug ID: 3903
                CC: bos at serpentine.com, mercurial-devel at selenic.com,
                    mpm at selenic.com
          Assignee: bugzilla at selenic.com
           Summary: Ancient glibc + parallel updates can cause manifest
                    corruption during rebases
          Severity: bug
    Classification: Unclassified
                OS: Linux
          Reporter: sid0 at fb.com
          Hardware: PC
            Status: UNCONFIRMED
           Version: unspecified
         Component: Mercurial
           Product: Mercurial

We've seen this with our deployment. When all of the following conditions are
met:
(a) one is using a Mercurial with parallel updates
(b) one is using a sufficiently ancient glibc (the glibc in CentOS 5.2, version
2.5-24.el5_2.2, exhibits the issue, but the glibc in CentOS 5.6, version
2.5-58.el5_6.4 doesn't)
(c) one performs a rebase across several thousand revs in a large repo

the rebase has a very small chance of producing a corrupt manifest.

-- 
You are receiving this mail because:
You are on the CC list for the bug.