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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 16 Mar 2007 13:38:53 -0700 From: Jeremy Fitzhardinge <jeremy@...p.org> To: David Miller <davem@...emloft.net> CC: mingo@...e.hu, ak@....de, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org, xen-devel@...ts.xensource.com, chrisw@...s-sol.org, zach@...are.com, rusty@...tcorp.com.au, anthony@...emonkey.ws, torvalds@...ux-foundation.org, NetDev <netdev@...r.kernel.org> Subject: Re: [patch 13/26] Xen-paravirt_ops: Consistently wrap paravirt ops callsites to make them patchable David Miller wrote: > Perhaps the problem can be dealt with using ELF relocations. > > There is another case, discussed yesterday on netdev, where run-time > resolution of ELF relocations would be useful (for > very-very-very-read-only variables) so if it can solve this problem > too it would be nice to have a generic infrastructure for it. That's an interesting idea. Have you or anyone else looked at what it would take to code up? For this case, I guess you'd walk the relocs looking for references into the paravirt_ops structure. You'd need to check that was a reference from an indirect jump or call instruction, which would identify a patchable callsite. The offset into the pv_ops structure would identify which operation is involved. That would be enough to use the existing paravirt_ops patch machinery to insert a patch, though it doesn't provide quite as much information as the current scheme. The current scheme also tells us how much space is available for patching over, and what registers the patched-in code can use/clobber. What are the netdev requirements? J - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists