[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1335708011.28106.245.camel@gandalf.stny.rr.com>
Date: Sun, 29 Apr 2012 10:00:11 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Sasha Levin <levinsasha928@...il.com>
Cc: "Eric W. Biederman" <ebiederm@...ssion.com>,
viro@...iv.linux.org.uk, fweisbec@...il.com, mingo@...hat.com,
a.p.zijlstra@...llo.nl, paulus@...ba.org, acme@...stprotocols.net,
james.l.morris@...cle.com, akpm@...ux-foundation.org,
tglx@...utronix.de, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH 01/14] sysctl: provide callback for write into ctl_table
entry
On Sun, 2012-04-29 at 14:07 +0200, Sasha Levin wrote:
> On Sun, Apr 29, 2012 at 10:22 AM, Eric W. Biederman
> Exactly twp of the patches (out of 14) are taking updates out of
> locks. I'm quite sure that doing that in the ftrace case is perfectly
> fine, and I'll take a second look at the sched-rt one since there
> indeed might be a race caused due to the patch that I've missed.
The update of ftrace_enable must be done under the ftrace_lock mutex.
With the exception of ftrace_kill() which is a one shot deal that kills
ftrace updates until a reboot.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists