Systemd/src/fuzz/fuzz-journald-stream.c
Zbigniew Jędrzejewski-Szmek eafadd069c fuzz-journal-stream: avoid assertion failure on samples which don't fit in pipe
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11587.
We had a sample which was large enough that write(2) failed to push all the
data into the pipe, and an assert failed. The code could be changed to use
a loop, but then we'd need to interleave writes and sd_event_run (to process
the journal). I don't think the complexity is worth it — fuzzing works best
if the sample is not too huge anyway. So let's just reject samples above 64k,
and tell oss-fuzz about this limit.
2019-02-26 13:00:35 +01:00

37 lines
1.1 KiB
C

/* SPDX-License-Identifier: LGPL-2.1+ */
#include <linux/sockios.h>
#include <sys/ioctl.h>
#include "fd-util.h"
#include "fuzz.h"
#include "fuzz-journald.h"
#include "journald-stream.h"
static int stream_fds[2] = { -1, -1 };
int LLVMFuzzerTestOneInput(const uint8_t *data, size_t size) {
Server s;
StdoutStream *stream;
int v;
if (size == 0 || size > 65536)
return 0;
if (!getenv("SYSTEMD_LOG_LEVEL"))
log_set_max_level(LOG_CRIT);
assert_se(socketpair(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0, stream_fds) >= 0);
dummy_server_init(&s, NULL, 0);
assert_se(stdout_stream_install(&s, stream_fds[0], &stream) >= 0);
assert_se(write(stream_fds[1], data, size) == (ssize_t) size);
while (ioctl(stream_fds[0], SIOCINQ, &v) == 0 && v)
sd_event_run(s.event, (uint64_t) -1);
if (s.n_stdout_streams)
stdout_stream_destroy(stream);
server_done(&s);
stream_fds[1] = safe_close(stream_fds[1]);
return 0;
}