Gary Lin 0e8c17fd80 bpfilter: Specify the log level for the kmsg message ... [ Upstream commit a196fa78a2 ] Per the kmsg document [0], if we don't specify the log level with a prefix "<N>" in the message string, the default log level will be applied to the message. Since the default level could be warning(4), this would make the log utility such as journalctl treat the message, "Started bpfilter", as a warning. To avoid confusion, this commit adds the prefix "<5>" to make the message always a notice. [0] https://www.kernel.org/doc/Documentation/ABI/testing/dev-kmsg Fixes: 36c4357c63 ("net: bpfilter: print umh messages to /dev/kmsg") Reported-by: Martin Loviska <mloviska@suse.com> Signed-off-by: Gary Lin <glin@suse.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Acked-by: Dmitrii Banshchikov <me@ubique.spb.ru> Link: https://lore.kernel.org/bpf/20210623040918.8683-1-glin@suse.com Signed-off-by: Sasha Levin <sashal@kernel.org>		2021-07-14 16:53:33 +02:00
..
.gitignore	…
Kconfig	init/Kconfig: add CONFIG_CC_CAN_LINK	2019-07-08 02:25:59 +09:00
Makefile	…
bpfilter_kern.c	signal/bpfilter: Fix bpfilter_kernl to use send_sig not force_sig	2019-05-27 09:36:28 -05:00
bpfilter_umh_blob.S	…
main.c	bpfilter: Specify the log level for the kmsg message	2021-07-14 16:53:33 +02:00
msgfmt.h	…