Re: [RFC PATCH 6/9] livepatch: create per-task consistency model

[Peter Zijlstra <peterz@infradead.org>]

On Thu, Feb 12, 2015 at 06:51:49AM -0600, Josh Poimboeuf wrote:
> > > To provide some background, I'm looking for a way to temporarily prevent
> > > a sleeping task from running while its stack is examined, to decide
> > > whether it can be safely switched to the new patching "universe".  For
> > > more details see klp_transition_task() in the patch below.
> > > 
> > > Using task_rq_lock() is the most straightforward way I could find to
> > > achieve that.
> > 
> > Its not at all clear how all this would work to me. And I'm not
> > motivated enough to go try and reverse engineer your patch;
> 
> The short answer is: I need a way to ensure that a task isn't sleeping
> on any of the functions we're trying to patch.  If it's not, then I can
> switch the task over to start using new versions of functions.
> 
> Obviously, there are many more details than that.  If you have specific
> questions I can try to answer them.

How can one task run new and another task old functions? Once you patch
any indirect function pointer any task will see the new call.

And what's wrong with using known good spots like the freezer?