diff options
| author | David Daney <[email protected]> | 2011-12-20 01:42:42 +0000 |
|---|---|---|
| committer | Steven Rostedt <[email protected]> | 2012-01-06 22:06:42 +0000 |
| commit | 2e885057b7f75035f0b85e02f737891482815a81 (patch) | |
| tree | 7b38008e2327ccc1536915f93762d0094862305c /fs/jbd/commit.c | |
| parent | Linux 3.2 (diff) | |
| download | kernel-2e885057b7f75035f0b85e02f737891482815a81.tar.gz kernel-2e885057b7f75035f0b85e02f737891482815a81.zip | |
recordmcount: Fix handling of elf64 big-endian objects.
In ELF64, the sh_flags field is 64-bits wide. recordmcount was
erroneously treating it as a 32-bit wide field. For little endian
objects this works because the flags of interest (SHF_EXECINSTR)
reside in the lower 32 bits of the word, and you get the same result
with either a 32-bit or 64-bit read. Big endian objects on the
other hand do not work at all with this error.
The fix: Correctly treat sh_flags as 64-bits wide in elf64 objects.
The symptom I observed was that my
__start_mcount_loc..__stop_mcount_loc was empty even though ftrace
function tracing was enabled.
Link: http://lkml.kernel.org/r/[email protected]
Cc: [email protected] # 3.0+
Signed-off-by: David Daney <[email protected]>
Signed-off-by: Steven Rostedt <[email protected]>
Diffstat (limited to 'fs/jbd/commit.c')
0 files changed, 0 insertions, 0 deletions
