aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorMarek Olšák <[email protected]>2011-06-10 14:41:26 +0000
committerDave Airlie <[email protected]>2011-06-14 10:59:03 +1000
commita27bb4b209dd6c327fa4e7185f2487f9508a58db (patch)
tree2c4ff2f2ded3beaaa74ef16047d5ab405e30d906 /tools/perf/util/scripting-engines/trace-event-python.c
parentab21e60beaa96f2c55604f633dfe74076c531df7 (diff)
drm/radeon/kms: do bounds checking for 3D_LOAD_VBPNTR and bump array limit
To my knowledge, the limit is 16 on r300. (the docs don't say what the limit is) The lack of bounds checking can be abused to do all sorts of things (from bypassing parts of the CS checker to crashing the kernel). Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=36745 Cc: [email protected] Signed-off-by: Marek Olšák <[email protected]> Signed-off-by: Dave Airlie <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions