Bernd Edlinger a75e78f21f kernfs: Fix range checks in kernfs_get_target_path ... The terminating NUL byte is only there because the buffer is allocated with kzalloc(PAGE_SIZE, GFP_KERNEL), but since the range-check is off-by-one, and PAGE_SIZE==PATH_MAX, the returned string may not be zero-terminated if it is exactly PATH_MAX characters long. Furthermore also the initial loop may theoretically exceed PATH_MAX and cause a fault. Signed-off-by: Bernd Edlinger <bernd.edlinger@hotmail.de> Acked-by: Tejun Heo <tj@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2018-09-16 22:38:57 +02:00
..
dir.c	kernfs: allow creating kernfs objects with arbitrary uid/gid	2018-07-20 23:44:35 -07:00
file.c	kernfs: allow creating kernfs objects with arbitrary uid/gid	2018-07-20 23:44:35 -07:00
inode.c	kernfs: allow creating kernfs objects with arbitrary uid/gid	2018-07-20 23:44:35 -07:00
Kconfig	kernfs: add CONFIG_KERNFS	2014-02-07 16:08:57 -08:00
kernfs-internal.h	kernfs: allow creating kernfs objects with arbitrary uid/gid	2018-07-20 23:44:35 -07:00
Makefile	sysfs, kernfs: add skeletons for kernfs	2013-11-27 13:28:24 -08:00
mount.c	kernfs: deal with kernfs_fill_super() failures	2018-05-21 14:30:08 -04:00
symlink.c	kernfs: Fix range checks in kernfs_get_target_path	2018-09-16 22:38:57 +02:00