[lkml]   [2013]   [Jul]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [for-next-3.11][PATCH 8/8] ftrace: Clear module traced functions on unload module
On Tue, 2013-07-30 at 07:27 -0400, Steven Rostedt wrote:

> The solution here is on module unload, look at all the registered funtion
> callbacks and remove any hash entry that points to any function in the
> module that is about to be removed.

There's another bug that is very similar to this one. I originally did a
ref count to ops, but I didn't really like it (it was included in what
Steve tested). While looking at other solutions I think I have something
that may be a bit better. It wont clear the trace on module reload, but
it can reenable the trace if a module is loaded with a function at the
same address that was traced before.

Sure this may be a bit confusing if another module gets traced, but it
allows for tracing functions on module load, which is useful.

I'm working on a new patch and hopefully Steve can test that one too.


-- Steve

 \ /
  Last update: 2013-07-30 20:01    [W:1.606 / U:0.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site