| 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: <1260852089.3541.5.camel@iscandar.digidescorp.com> Date: Mon, 14 Dec 2009 22:41:28 -0600 From: "Steven J. Magnani" <steve@...idescorp.com> To: microblaze-uclinux@...e.uq.edu.au Cc: linux-kernel@...r.kernel.org, monstr@...str.eu Subject: RE: [microblaze-uclinux] [PATCH v2] microblaze: nommu: Don't clobber R11 on syscalls On Mon, 2009-12-14 at 14:50 -0800, Jim Van Vorst wrote: > Isn't R11 a temporary? If it doesn't need to be preserved across function > calls, why can't it be clobbered during a syscall? Because the Microblaze syscall macros don't include r11 in the clobber list. I suppose an alternative solution would just change the userspace macros and not the kernel, even though there is a bug in the kernel. Michal, is the Microblaze ABI considered "locked down" now, or is a kernel solution still permitted? ------------------------------------------------------------------------ Steven J. Magnani "I claim this network for MARS! www.digidescorp.com Earthling, return my space modulator!" #include <standard.disclaimer> -- 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