| 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: <p73wsr7ef1h.fsf@bingen.suse.de> Date: Sat, 22 Dec 2007 01:42:02 +0100 From: Andi Kleen <andi@...stfloor.org> To: David Miller <davem@...emloft.net> Cc: mtk.manpages@...glemail.com, akpm@...ux-foundation.org, lkml@...idb.org, paulus@...ba.org, drepper@...hat.com, cfriesen@...tel.com, schwab@...e.de, linux-kernel@...r.kernel.org Subject: Re: compat_sys_times() bogus until jiffies >= 0. David Miller <davem@...emloft.net> writes: > Only on x86 platforms. Sparc, IA64, MIPS, powerpc, etc. all get this > case right. Do they for 32bit kernels or for 64bit userland? > Yes it's another unfortunate side effect of how error status is > indicated for x86 system calls. Maybe I'm dense, but doesn't all the kernel code pass it the same way as the x86 syscall code? For your proposal you would need a separate error bit coming out of the sys_* to handle this case. Basically rewrite all code that ever returns errors in the kernel. Or do I miss something? Or are you talking about solving it only for 32bit compat emulation on 64bit kernels? There it would be possible, but only doing it there and not on native 32bit systems wouldn't seem clean to me. At least on x86-64 the compat code's (near) only goal in live is to be as compatible to 32it as possible not better. -Andi -- 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