aboutsummaryrefslogtreecommitdiff
path: root/arch/x86/crypto/twofish-x86_64-asm_64.S
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2009-02-07 19:38:43 -0500
committerSteven Rostedt <srostedt@redhat.com>2009-02-07 19:38:43 -0500
commit1830b52d0de8c60c4f5dfbac134aa8f69d815801 (patch)
tree2aa803853ac145fedd0d65324d77f64d25e7b3a2 /arch/x86/crypto/twofish-x86_64-asm_64.S
parent43769f10b4826376cbf4ce17af74a5b4e8dc4fcd (diff)
trace: remove deprecated entry->cpu
Impact: fix to prevent developers from using entry->cpu With the new ring buffer infrastructure, the cpu for the entry is implicit with which CPU buffer it is on. The original code use to record the current cpu into the generic entry header, which can be retrieved by entry->cpu. When the ring buffer was introduced, the users were convert to use the the cpu number of which cpu ring buffer was in use (this was passed to the tracers by the iterator: iter->cpu). Unfortunately, the cpu item in the entry structure was never removed. This allowed for developers to use it instead of the proper iter->cpu, unknowingly, using an uninitialized variable. This was not the fault of the developers, since it would seem like the logical place to retrieve the cpu identifier. This patch removes the cpu item from the entry structure and fixes all the users that should have been using iter->cpu. Signed-off-by: Steven Rostedt <srostedt@redhat.com>
Diffstat (limited to 'arch/x86/crypto/twofish-x86_64-asm_64.S')
0 files changed, 0 insertions, 0 deletions