diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2014-10-28 13:27:19 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2014-10-28 13:27:19 -0700 |
commit | 6234056e1380e72f316546cba13d0f8f09b29789 (patch) | |
tree | 878abf152e7117cdeb9ba6159aa07506798de571 /fs/nfsd/nfs4proc.c | |
parent | 6e2028aaa1373081e553d4442736ce0d1dd279e8 (diff) | |
parent | 4fc409048d5afb1ad853f294b4262ecf2c980a49 (diff) | |
download | op-kernel-dev-6234056e1380e72f316546cba13d0f8f09b29789.zip op-kernel-dev-6234056e1380e72f316546cba13d0f8f09b29789.tar.gz |
Merge tag 'trace-fixes-v3.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace
Pull ftrace trampoline accounting fixes from Steven Rostedt:
"Adding the new code for 3.19, I discovered a couple of minor bugs with
the accounting of the ftrace_ops trampoline logic.
One was that the old hash was not updated before calling the modify
code for an ftrace_ops. The second bug was what let the first bug go
unnoticed, as the update would check the current hash for all
ftrace_ops (where it should only check the old hash for modified
ones). This let things work when only one ftrace_ops was registered
to a function, but could break if more than one was registered
depending on the order of the look ups.
The worse thing that can happen if this bug triggers is that the
ftrace self checks would find an anomaly and shut itself down"
* tag 'trace-fixes-v3.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
ftrace: Fix checking of trampoline ftrace_ops in finding trampoline
ftrace: Set ops->old_hash on modifying what an ops hooks to
Diffstat (limited to 'fs/nfsd/nfs4proc.c')
0 files changed, 0 insertions, 0 deletions