| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <ad0732bf-9042-4659-a107-348340016351@email.android.com> Date: Wed, 20 Nov 2013 10:30:56 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: Andi Kleen <andi@...stfloor.org> CC: x86@...nel.org, linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH] Add a text_poke syscall Why? Live patching works fine and keys the other threads run along just fine. We do this for ftrace already... Andi Kleen <andi@...stfloor.org> wrote: >"H. Peter Anvin" <hpa@...or.com> writes: >> >> We're talking user space here, which has different requirement (COW, >> memory protection, ...) which means it is not really the same code. >You >> can't take a page fault while patching the kernel. > >The syscall pins the page, then it calls the kernel code. >There are no page faults during patching. > >> I'm referring to if some thread actually stumbles over INT 3, which >is >> indeed not very long for one patch site (as long as you don't end up >> with page faults.) However, for tracing, you may want to do tens of >> thousands of patches, and you really want to batch them. > >For tens of thousand of patches you very likely don't want >live patching, but a stop everything approach. > >-Andi -- Sent from my mobile phone. Please pardon brevity and lack of formatting. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists