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: Thu, 10 Jan 2019 16:02:53 +0800 From: Zhenzhong Duan <zhenzhong.duan@...cle.com> To: LKML <linux-kernel@...r.kernel.org> Cc: Peter Zijlstra <peterz@...radead.org>, longman@...hat.com, SRINIVAS <srinivas.eeda@...cle.com> Subject: Question about qspinlock nest Hi Maintainer, There is a question confused me for days. Appreciate an answer. In below code, the comment says we never have more than 4 nested contexts. What happen if debug and mce exceptions nest with the four, or we ensure it never happen? /* * Per-CPU queue node structures; we can never have more than 4 nested * contexts: task, softirq, hardirq, nmi. * * Exactly fits one 64-byte cacheline on a 64-bit architecture. * * PV doubles the storage and uses the second cacheline for PV state. */ static DEFINE_PER_CPU_ALIGNED(struct qnode, qnodes[MAX_NODES]); -- Thanks Zhenzhong
Powered by blists - more mailing lists