Re: [PATCH x86_64] Live Patching Function on

From: Takashi Ikebe
Date: Sun Apr 24 2005 - 21:13:06 EST

Andi Kleen wrote:

>Takashi Ikebe <ikebe.takashi@xxxxxxxxxxxxx> writes:
>>The patch was over 50k, so I separate it to each architecture and in line..
>>This patch add function called "Live patching" which is defined on
>>OSDL's carrier grade linux requiremnt definition to linux kernel.
>>The live patching allows process to patch on-line (without restarting
>>process) on i386 and x86_64 architectures, by overwriting jump assembly
>>code on entry point of functions which you want to fix, to patched
>How exactly is this different from ptrace?
>Seems just like a ptrace memcpy extension
>Is the patching really that time critical that you cant do it
>with normal ptrace?
Only few patch modules are not so critical, however sometimes large
number of patches are applied at one time. In that case, time is very
critical with normal ptrace. As you know, normal ptrace need to target
process STOP whenever change the memory/registers.
Our approach is "do not stop the target process's execution as possible
as", because the target process can provide service during patch on SMP
machine (do not want to stop service due to patch).
If we load hundreds of patch modules at one time, I think it will goes
quite time critical..

>>+ if(((current->uid != tsk->euid) ||
>>+ (current->uid != tsk->suid) ||
>>+ (current->uid != tsk->uid) ||
>>+ (current->gid != tsk->egid) ||
>>+ (current->gid != tsk->sgid) ||
>>+ (current->gid != tsk->gid)) && !capable(CAP_SYS_PANNUS)) {
>>+ // invalid user in sys_accesspvm
>>+ return -EPERM;
>>+ }
>>+> + p = vmalloc(len);
>This needs a limit.
Thank you, we'll fix this soon.

>>--- linux- 2005-04-08 03:57:30.000000000 +0900
>>+++ linux- 2005-04-18 10:45:47.000000000 +0900
>>@@ -214,6 +214,8 @@ sysret_check:
>> /* Handle reschedules */
>> /* edx: work, edi: workmask */
>> sysret_careful:
>>+ cmpl $0,threadinfo_inipending(%rcx)
>>+ jne sysret_init
>Put the check into the normal notify_resume work mask, not adding
>a separate check into this critical fast path.
OK, we'll fix this soon.

>> /*
>>+ * In the case restorer calls rt_handlereturn, collect and store registers,
>>+ * and call rt_handlereturn with stored register struct.
>>+ */
>This seems quite pointless since ptrace and can change all registers
>in a child.
Well, this can change as you said, but I think, this makes target
process stopping time increase.
Because, to control target process's (patch module's) initialization,
the command process should know the target process's status and then
stop with ptrace.
Currently rt_handlereturn works on target process's context like signal
handler return, so, I think there is minimum time loss on target process.
If command process controls the target process's initialization, this
seems target process's stopping time increasing.
Well, may be our idea is wrong, please tell us.

Thank you your advice!

>Didnt review more.

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 : ikebe.takashi@xxxxxxxxxxxxx

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