diff options
| author | Arnd Bergmann <[email protected]> | 2015-11-20 18:26:07 +0100 |
|---|---|---|
| committer | Ohad Ben-Cohen <[email protected]> | 2015-11-26 10:07:53 +0200 |
| commit | 92792e48e2ae6051af30468a87994b5432da2f06 (patch) | |
| tree | 3e35802656103fb2b4671e660c8dbdadf62066cd /tools/perf/util/trace-event-scripting.c | |
| parent | 1ec218373b8ebda821aec00bb156a9c94fad9cd4 (diff) | |
remoteproc: avoid stack overflow in debugfs file
Recent gcc versions warn about reading from a negative offset of
an on-stack array:
drivers/remoteproc/remoteproc_debugfs.c: In function 'rproc_recovery_write':
drivers/remoteproc/remoteproc_debugfs.c:167:9: warning: 'buf[4294967295u]' may be used uninitialized in this function [-Wmaybe-uninitialized]
I don't see anything in sys_write() that prevents us from
being called with a zero 'count' argument, so we should
add an extra check in rproc_recovery_write() to prevent the
access and avoid the warning.
Signed-off-by: Arnd Bergmann <[email protected]>
Fixes: 2e37abb89a2e ("remoteproc: create a 'recovery' debugfs entry")
Signed-off-by: Ohad Ben-Cohen <[email protected]>
Diffstat (limited to 'tools/perf/util/trace-event-scripting.c')
0 files changed, 0 insertions, 0 deletions