lkml.org 
[lkml]   [2019]   [Oct]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH v3 5/6] x86/ftrace: Use text_poke()
    From
    Date
    On 10/15/19 11:31 AM, Jessica Yu wrote:
    > +++ Joe Lawrence [15/10/19 11:06 -0400]:
    >> On 10/15/19 10:13 AM, Miroslav Benes wrote:
    >>> 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? :)
    >

    Livepatching folks -- I don't have the LPC summary link (etherpad?) that
    Jiri put together. Does someone have that handy for Jessica?

    Thanks,

    -- Joe

    \
     
     \ /
      Last update: 2019-10-16 00:18    [W:4.201 / U:0.008 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site