-
- Downloads
journal: Don't write to journal files without the new boot ID update behavior guarantee
With the old boot ID update behavior there's no way to compare the boot ID of a new entry to be written with the boot ID of the last entry in the journal in a performant manner, and therefore no way to determine if monotonic clock value consistency checking is needed. Refuse to open journal files without the new boot ID update behavior guarantee to simplify consistency checking. (cherry picked from commit 2f766aca1e1398288e01b26a69eb02a7b831ab00)
Loading
Please register or sign in to comment