| 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: <20090322114237.GB570@1wt.eu> Date: Sun, 22 Mar 2009 12:42:37 +0100 From: Willy Tarreau <w@....eu> To: Dragoslav Zaric <dragoslav.zaric.kd@...il.com> Cc: LKML <linux-kernel@...r.kernel.org> Subject: Re: Test some kernel feature without recompile On Sun, Mar 22, 2009 at 11:43:28AM +0100, Dragoslav Zaric wrote: > Hi, > > I know when you work on some kernel module, you can change code and load > module again and test it, but what if you change some built in kernel > .c file, why > would I need to recompile whole kernel just to see what happens if I change one > .c file ?? > > Why can I just compile one changed .c file and copy it where compiled version of > that file reside inside kernel tree? Or maybe there is some image info embedded > inside compiled files, so that file must belong to specific image from > which it is > installed ? Well, in some cases you can do that. For very minor changes (constants, disabling 'if' statements, breaking out of loops, or returning from functions), tampering the memory with an hex editor is often more convenient than rebooting. /proc/ksyms is your friend here. It also sometimes help you see the effect of your changes. But you must always be ready to reboot anyway because mistakes are quite common and generally don't leave you with a second chance. Willy -- 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