Benjamin Gray 5efb685bb3 initramfs: Check negative timestamp to prevent broken cpio archive ... Similar to commit 4c9d410f32 ("initramfs: Check timestamp to prevent broken cpio archive"), except asserts that the timestamp is non-negative. This can happen when the KBUILD_BUILD_TIMESTAMP is a value before UNIX epoch, which may be set when making reproducible builds that don't want to look like they use a valid date. While support for dates before 1970 might not be supported, this is more about preventing undetected CPIO corruption. The printf's use a minimum length format specifier, and will happily make the field longer than 8 characters if they need to. Signed-off-by: Benjamin Gray <bgray@linux.ibm.com> Reviewed-by: Andrew Donnellan <ajd@linux.ibm.com> Tested-by: Andrew Donnellan <ajd@linux.ibm.com> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>		2023-04-16 17:37:01 +09:00
..
dummy-include	kbuild: prevent exported headers from including <stdlib.h>, <stdbool.h>	2022-05-13 10:56:10 +02:00
include	Kbuild updates for v5.19	2022-05-26 12:09:50 -07:00
.gitignore	.gitignore: prefix local generated files with a slash	2021-05-02 00:43:35 +09:00
default_cpio_list
gen_init_cpio.c	initramfs: Check negative timestamp to prevent broken cpio archive	2023-04-16 17:37:01 +09:00
gen_initramfs.sh	kbuild: replace LANG=C with LC_ALL=C	2021-05-02 00:43:35 +09:00
initramfs_data.S
Kconfig
Makefile	kbuild: unify cmd_copy and cmd_shipped	2022-02-14 10:37:32 +09:00