+++ Joe Lawrence [15/10/19 11:06 -0400]:

On 10/15/19 10:13 AM, Miroslav Benes wrote:

quoted

Yes, it does. klp_module_coming() calls module_disable_ro() on all
patching modules which patch the coming module in order to call
apply_relocate_add(). New (patching) code for a module can be relocated
only when the relevant module is loaded.

FWIW, would the LPC blue-sky2 model (ie, Steve's suggestion @ 
plumber's where livepatches only patch a single object and updates are 
kept on disk to handle coming module updates as they are loaded) 
eliminate those outstanding relocations and the need to perform this 
late permission flipping?

I wasn't at Plumbers sadly, was this idea documented/talked about in
detail somewhere? (recording, slides, etherpad, etc?). What do you
mean by updates are kept on disk? Maybe someone can explain it more
in detail? :)