| 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
| ||
|
Date: Wed, 11 Oct 2006 10:58:21 -0600 From: ebiederm@...ssion.com (Eric W. Biederman) To: "Aneesh Kumar K.V" <aneesh.kumar@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: safe_smp_processor_id i386 and x86_64 "Aneesh Kumar K.V" <aneesh.kumar@...il.com> writes: > I was looking at the git log and the below changes confused me. They are being used to solve different problems. smp_processor_id on i386 doesn't work when a stack overflow occurs. safe_smp_processor_id does. On x86_64 since it is a simple register value we don't have that problem. Eric - 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