| 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: <87vcdpk3lz.fsf@xmission.com> Date: Thu, 01 Nov 2012 03:40:56 -0700 From: ebiederm@...ssion.com (Eric W. Biederman) To: Mitsuhiro Tanino <mitsuhiro.tanino.gm@...achi.com> Cc: Vivek Goyal <vgoyal@...hat.com>, kexec@...ts.infradead.org, linux-kernel@...r.kernel.org Subject: Re: [Patch 0/2] Exclude hwpoison page from vmcore dump Mitsuhiro Tanino <mitsuhiro.tanino.gm@...achi.com> writes: > Hi Vivek, > > (2012/10/31 23:14), Vivek Goyal wrote: >> If hwpoision functionality is not available in hardware, then respective >> bit will not be even set in struct page and it will be saved by default. >> So it should not matter whether hardware has hwpoision functionality >> or not. > > Thanks, I understand. > >> I think that removing hwpoisno pages by default makes sense. If somebody >> does have a reasonable case of not doing so, then we could either >> introduce anther filtering level (based on type) or add another command >> line option like (--no-hwposion-filtering) etc. > > I agree with you. > If somebody requests to support for disabling the filter of hwpoison pages, > this option will be discussed. I agree. If we are performing filtering filtering out of poisoned pages seems very reasonable. So ack on the basic concept. 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