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: Tue, 19 Apr 2016 19:13:34 +0800 From: Xishi Qiu <qiuxishi@...wei.com> To: Linux MM <linux-mm@...ck.org>, LKML <linux-kernel@...r.kernel.org>, Naoya Horiguchi <n-horiguchi@...jp.nec.com> CC: Xishi Qiu <qiuxishi@...wei.com> Subject: mce: a question about memory_failure_early_kill in memory_failure() /proc/sys/vm/memory_failure_early_kill 1: means kill all processes that have the corrupted and not reloadable page mapped. 0: means only unmap the corrupted page from all processes and only kill a process who tries to access it. If set memory_failure_early_kill to 0, and memory_failure() has been called. memory_failure() hwpoison_user_mappings() collect_procs() // the task(with no PF_MCE_PROCESS flag) is not in the tokill list try_to_unmap() If the task access the memory, there will be a page fault, so the task can not access the original page again, right? Thanks, Xishi Qiu
Powered by blists - more mailing lists