Re: [PATCH v2] livepatch/rcu: Fix stacking of patches when RCU infrastructure is patched

I've slightly adjusted the changelog and comment (as noted by Miroslav) a little bit and queued for 4.12. Thanks, -- Jiri Kosina SUSE Labs

Re: [PATCH v2] livepatch/rcu: Fix stacking of patches when RCU infrastructure is patched

On Wed, 14 Jun 2017, Petr Mladek wrote: > rcu_read_(un)lock(), list_*_rcu(), and synchronize_rcu() are used for > a secure access and manipulation of the list of patches that modify > the same function. In particular, it is the variable func_stack that > is accessible from the ftrace handler via s

Re: [PATCH v2] livepatch/rcu: Fix stacking of patches when RCU infrastructure is patched

On Wed, Jun 14, 2017 at 10:54:52AM +0200, Petr Mladek wrote: > rcu_read_(un)lock(), list_*_rcu(), and synchronize_rcu() are used for > a secure access and manipulation of the list of patches that modify > the same function. In particular, it is the variable func_stack that > is accessible from the

[PATCH v2] livepatch/rcu: Fix stacking of patches when RCU infrastructure is patched

rcu_read_(un)lock(), list_*_rcu(), and synchronize_rcu() are used for a secure access and manipulation of the list of patches that modify the same function. In particular, it is the variable func_stack that is accessible from the ftrace handler via struct ftrace_ops and klp_ops. Of course, it sync