SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

journal: allow files with no data whatsoever

Browse Source 
If a file was opened for writing, and then closed immediately without
actually writing any entries, on subsequent opening, it would be
considered "corrupted". This should be totally fine, and even in
read mode, an empty file can become non-empty later on.
This commit is contained in:
Zbigniew Jędrzejewski-Szmek
2014-07-15 22:23:47 -04:00
parent b7e6c03d3b
commit b3306e9c3c
1 changed files with 0 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/journal/journal-file.c
-6
View File
@@ -279,12 +279,6 @@ static int journal_file_verify_header(JournalFile *f) {
!VALID64(le64toh(f->header->entry_array_offset)))
return -ENODATA;
if (le64toh(f->header->data_hash_table_offset) < le64toh(f->header->header_size) ||
le64toh(f->header->field_hash_table_offset) < le64toh(f->header->header_size) ||
le64toh(f->header->tail_object_offset) < le64toh(f->header->header_size) ||
le64toh(f->header->entry_array_offset) < le64toh(f->header->header_size))
return -ENODATA;
if (f->writable) {
uint8_t state;
sd_id128_t machine_id;