linux-kernel - Re: [PATCH RFC 3/3] proc/smaps: show amount of hwpoison pages

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FA02603.80807@openvz.org>
Date:	Tue, 01 May 2012 22:05:55 +0400
From:	Konstantin Khlebnikov <khlebnikov@...nvz.org>
To:	KOSAKI Motohiro <kosaki.motohiro@...il.com>
CC:	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Andi Kleen <andi@...stfloor.org>
Subject: Re: [PATCH RFC 3/3] proc/smaps: show amount of hwpoison pages

KOSAKI Motohiro wrote:
> On Mon, Apr 30, 2012 at 7:29 AM, Konstantin Khlebnikov
> <khlebnikov@...nvz.org>  wrote:
>> This patch adds line "HWPoinson:<size>  kB" into /proc/pid/smaps if
>> CONFIG_MEMORY_FAILURE=y and some HWPoison pages were found.
>> This may be useful for searching applications which use a broken memory.
>
> I dislike "maybe useful" claim. If we don't know exact motivation of a feature,
> we can't maintain them especially when a bugfix can't avoid ABI change.
>
> Please write down exact use case.

I don't know how to exactly use this hw-poison stuff, but smaps suppose to
export state of ptes in vma. It seems to rational to show also hw-poisoned ptes,
since kernel has this feature and pte can be in hw-poisoned state.

and now everyone can easily find them:
# sudo grep HWPoison /proc/*/smaps
--
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/