]> git.ipfire.org Git - thirdparty/systemd.git/commit
projects / thirdparty / systemd.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: de965f4) | patch
test: test journalctl with corrupted journals 27458/head
authorFrantisek Sumsal <frantisek@sumsal.cz>
Sat, 29 Apr 2023 10:01:37 +0000 (12:01 +0200)
committerFrantisek Sumsal <frantisek@sumsal.cz>
Mon, 1 May 2023 08:14:12 +0000 (10:14 +0200)
commit0f69a4e9ae2b6916d9da4d47b67ac3e654b9f79e
treec3e73c7517a820b5e3a725b64fed6593ca9eecaftree | snapshot
parentde965f48934325e6fc564720aa318f24c315caeccommit | diff
test: test journalctl with corrupted journals

Last month I monkey-patched journald to produce a small (64K) but valid
journal and used that as an input to four AFL fuzzers. After a month it
generated quite a nice corpora (4738 test cases) and after filtering
and minimizing it I was left with 619 unique journals with various
levels of corruption that probe the journal code.

It seems to detect past issues like systemd#26567, etc.
test/test-journals/afl-corrupted-journals.tar.zst [new file with mode: 0644] blob
test/units/testsuite-04.sh diff | blob | blame | history
Unnamed repository; edit this file 'description' to name the repository.