[lkml]   [2005]   [Apr]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH x86_64] Live Patching Function on
    Chris Wedgwood wrote:

    >>On live patching, you never need to use shared memory, just prepare
    >>fixed code, and just compile it as shared ibject, that's all. pretty
    >>easy and fast to replace the functions.
    >it requires magic like a compiler and knowledge of the original
    Well, Live patching is just a patch, so I think the developer of patch
    should know the original source code well.

    >if the application was written sensibly someone without access to the
    >application code could change this live taking over the previous
    >applications state even more easily --- and the code would be more
    >straightforward. so i still fail to see why this is needed.
    Well, as you said some application can do that, but some application can
    not continue service with your suggestion.
    please think about the process which use connection type communication
    such as TCP(it's only example) between users and server. During status
    copy, all the session between users and server are disconnected... can
    not save the exiting service at all.
    It's one example, but similar problems may occurs whenever processed use
    the resources which are mainly controlled by kernel.

    Takashi Ikebe
    NTT Network Service Systems Laboratories
    9-11, Midori-Cho 3-Chome Musashino-Shi,
    Tokyo 180-8585 Japan
    Tel : +81 422 59 4246, Fax : +81 422 60 4012
    e-mail :

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-04-20 06:22    [W:0.036 / U:1.360 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site