Omar Ramirez Luna 7c256647b5 staging: tidspbridge: fix potential array out of bounds write ... The name of the firmware (drv_datap->base_img) could potentially become equal to 255 valid characters (size of exec_file), this will result in an out of bounds write, given that the 255 chars along with a '\0' terminator will be copied into an array of 255 chars. Produce an error on this cases, because the driver expects the NULL ending to be among the 255 char limit. Reported-by: Chen Gang <gang.chen@asianux.com> Signed-off-by: Omar Ramirez Luna <omar.ramirez@copitl.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2013-01-17 16:47:13 -08:00
..
core	staging: tidspbridge: use prepare/unprepare on dsp clocks	2013-01-07 15:03:56 -08:00
Documentation	staging: tidspbridge: Fix typos.	2012-08-13 19:06:59 -07:00
dynload	staging: tidspbridge: dynload: reloc.c: checkpatch.pl cleanup	2012-11-13 13:10:39 -08:00
gen	staging: tidspbridge: eliminate uuid_uuid_to_string	2012-08-13 19:06:59 -07:00
hw	staging: tidspbridge: delete unused mmu functions	2012-10-24 16:31:32 -07:00
include/dspbridge	arm: at91: mach header cleanup	2012-11-12 22:54:08 +01:00
pmgr	staging: tidspbridge: remove gh_init() and gh_exit()	2012-03-09 13:21:08 -08:00
rmgr	staging: tidspbridge: fix potential array out of bounds write	2013-01-17 16:47:13 -08:00
Kconfig	staging: tidspbridge: always compile dsp wdt code	2012-02-24 12:05:38 -08:00
Makefile	staging: tidspbridge: Rename module from bridgedriver to tidspbridge	2012-02-09 09:37:11 -08:00
TODO	staging: tidspbridge: remove custom linked list	2011-02-04 20:11:41 -06:00