Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758589Ab2EASPW (ORCPT ); Tue, 1 May 2012 14:15:22 -0400 Received: from mail-yw0-f46.google.com ([209.85.213.46]:33362 "EHLO mail-yw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758555Ab2EASPS convert rfc822-to-8bit (ORCPT ); Tue, 1 May 2012 14:15:18 -0400 MIME-Version: 1.0 In-Reply-To: <4FA02603.80807@openvz.org> References: <20120430112903.14137.81692.stgit@zurg> <20120430112910.14137.28935.stgit@zurg> <4FA02603.80807@openvz.org> From: KOSAKI Motohiro Date: Tue, 1 May 2012 14:14:57 -0400 Message-ID: Subject: Re: [PATCH RFC 3/3] proc/smaps: show amount of hwpoison pages To: Konstantin Khlebnikov Cc: "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , Andrew Morton , Andi Kleen Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1504 Lines: 38 On Tue, May 1, 2012 at 2:05 PM, Konstantin Khlebnikov wrote: > KOSAKI Motohiro wrote: >> >> On Mon, Apr 30, 2012 at 7:29 AM, Konstantin Khlebnikov >> ?wrote: >>> >>> This patch adds line "HWPoinson: ?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 First, I don't think "we can expose it" is good reason. Second, hw-poisoned mean such process is going to be killed at next page touch. But I can't imagine anyone can use its information because it's racy against process kill. I think admin should use mce log. So, until we find a good use case, I don't ack this. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/