diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-02-27 00:07:29 -0500 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2014-03-05 00:17:27 -0500 |
| commit | fb099c8d2af6620db2709e826a258089d10cdfe8 (patch) | |
| tree | 1af39090260dd92db522636b7f3d86d69b95ef6f /units/user.slice | |
| parent | 32f244309902243a20cff5d5d1abb1c888b5fb21 (diff) | |
journal: assume that next entry is after previous entry
With a corrupted file, we can get in a situation where two entries
in the entry array point to the same object. Then journal_file_next_entry
will find the first one using generic_arrray_bisect, and try to move to
the second one, but since the address is the same, generic_array_get will
return the first one. journal_file_next_entry ends up in an infinite loop.
https://bugzilla.redhat.com/show_bug.cgi?id=1047039
Diffstat (limited to 'units/user.slice')
0 files changed, 0 insertions, 0 deletions