summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorJiri Olsa <jolsa@redhat.com>2011-05-10 12:43:46 +0200
committerSteven Rostedt <rostedt@goodmis.org>2011-05-26 01:56:36 +0200
commit7cbc5b8d4a775a43875a09e29c49a2a8195b5b2d (patch)
treeb172a445ca84bd463abc6006233799e0a5f422b2 /drivers
parentftrace/recordmcount: Avoid STT_FUNC symbols as base on ARM (diff)
downloadlinux-7cbc5b8d4a775a43875a09e29c49a2a8195b5b2d.tar.xz
linux-7cbc5b8d4a775a43875a09e29c49a2a8195b5b2d.zip
jump_label: Check entries limit in __jump_label_update
When iterating the jump_label entries array (core or modules), the __jump_label_update function peeks over the last entry. The reason is that the end of the for loop depends on the key value of the processed entry. Thus when going through the last array entry, we will touch the memory behind the array limit. This bug probably will never be triggered, since most likely the memory behind the jump_label entries will be accesable and the entry->key will be different than the expected value. Signed-off-by: Jiri Olsa <jolsa@redhat.com> Acked-by: Jason Baron <jbaron@redhat.com> Link: http://lkml.kernel.org/r/20110510104346.GC1899@jolsa.brq.redhat.com Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions