From 874bc134ac6504c45e94174e37af13ff21a6bfe2 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Mon, 14 Jul 2014 16:53:23 -0400 Subject: Clear up confusion wrt. ENTRY_SIZE_MAX and DATA_SIZE_MAX Define DATA_SIZE_MAX to mean the maximum size of a single field, and ENTRY_SIZE_MAX to mean the size of the whole entry, with some rough calculation of overhead over the payload. Check if entries are not too big when processing native journal messages. --- src/journal/journald-native.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/journal/journald-native.h') diff --git a/src/journal/journald-native.h b/src/journal/journald-native.h index 97808e746a..e82a5b87d5 100644 --- a/src/journal/journald-native.h +++ b/src/journal/journald-native.h @@ -25,7 +25,7 @@ /* Make sure not to make this smaller than the maximum coredump * size. See COREDUMP_MAX in coredump.c */ -#define ENTRY_SIZE_MAX (1024*1024*768u) +#define ENTRY_SIZE_MAX (1024*1024*770u) #define DATA_SIZE_MAX (1024*1024*768u) bool valid_user_field(const char *p, size_t l, bool allow_protected); -- cgit v1.2.3-54-g00ecf