Files
systemd/test/units
Yu Watanabe 185e201690 journalctl: find boot ID more gracefully in corrupted journal
In discover_next_boot(), first we find a new boot ID based on the value
stored in the entry object. Then, find the tail (or head when we are going
upwards) entry of the boot based on the _BOOT_ID= field data.

If boot IDs of an entry in the entry object and _BOOT_ID field data
are inconsistent, which may happen on corrupted journal, then previously
discover_next_boot() failed with -ENODATA.

This makes the function check if the two boot IDs in each entry are
consistent, and skip the entry if not.

Fixes the failure of `journalctl -b -1` for 'truncated' journal:
https://github.com/systemd/systemd/pull/29334#issuecomment-1736567951
2023-10-02 10:59:33 +09:00
..
2023-07-04 21:55:53 +02:00
2023-05-24 20:06:10 +09:00
2023-08-12 10:13:56 +02:00
2023-09-27 14:50:19 +02:00
2023-05-26 00:45:54 -04:00
2023-08-23 15:12:23 +02:00
2022-08-23 10:53:47 +02:00
2022-08-23 10:53:47 +02:00
2023-09-19 21:45:27 +08:00
2023-09-27 14:50:19 +02:00