Re: [3.4-stable][PATCH 2/3] ftrace: Fix synchronization location disabling and freeing ftrace_ops

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2014-03-30 at 20:39 +0100, Ben Hutchings wrote:
> On Tue, 2014-02-11 at 14:49 -0500, Steven Rostedt wrote:
> > commit a4c35ed241129dd142be4cadb1e5a474a56d5464 upstream.
> > 
> > The synchronization needed after ftrace_ops are unregistered must happen
> > after the callback is disabled from becing called by functions.
> > 
> > The current location happens after the function is being removed from the
> > internal lists, but not after the function callbacks were disabled, leaving
> > the functions susceptible of being called after their callbacks are freed.
> > 
> > This affects perf and any externel users of function tracing (LTTng and
> > SystemTap).
> > 
> > Cc: stable@xxxxxxxxxxxxxxx # 3.0+
> > Fixes: cdbe61bfe704 "ftrace: Allow dynamically allocated function tracers"
> > Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx>
> [...]
> 
> I've queued this up for 3.2, but I needed to make further changes.  My
> version is below.
[...]

And I've queued up "ftrace: Have function graph only trace based on
global_ops filters" (commit 23a8e8441a0a upstream).

Ben.

-- 
Ben Hutchings
If more than one person is responsible for a bug, no one is at fault.

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Kernel]     [Kernel Development Newbies]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]