From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933044AbbCQRT3 (ORCPT ); Tue, 17 Mar 2015 13:19:29 -0400 Received: from forward-corp1f.mail.yandex.net ([95.108.130.40]:57628 "EHLO forward-corp1f.mail.yandex.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932801AbbCQRTY (ORCPT ); Tue, 17 Mar 2015 13:19:24 -0400 Authentication-Results: smtpcorp1m.mail.yandex.net; dkim=pass header.i=@yandex-team.ru Message-ID: <55086217.6060802@yandex-team.ru> Date: Tue, 17 Mar 2015 20:19:19 +0300 From: Konstantin Khlebnikov User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: "Kirill A. Shutemov" , Christian Borntraeger CC: linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm: trigger panic on bad page or PTE states if panic_on_oops References: <1426495021-6408-1-git-send-email-borntraeger@de.ibm.com> <20150316110033.GA20546@node.dhcp.inet.fi> <5506BAB6.3080104@de.ibm.com> <20150316121559.GB20546@node.dhcp.inet.fi> In-Reply-To: <20150316121559.GB20546@node.dhcp.inet.fi> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 16.03.2015 15:15, Kirill A. Shutemov wrote: > On Mon, Mar 16, 2015 at 12:12:54PM +0100, Christian Borntraeger wrote: >> Am 16.03.2015 um 12:00 schrieb Kirill A. Shutemov: >>> On Mon, Mar 16, 2015 at 09:37:01AM +0100, Christian Borntraeger wrote: >>>> while debugging a memory management problem it helped a lot to >>>> get a system dump as early as possible for bad page states. >>>> >>>> Lets assume that if panic_on_oops is set then the system should >>>> not continue with broken mm data structures. >>> >>> bed_pte is not an oops. >> >> I know that this is not an oops, but semantically it is like one. I certainly >> want to a way to hard stop the system if something like that happens. >> >> Would something like panic_on_mm_error be better? > > Or panic_on_taint= where is bit-mask of TAINT_* values. > > The problem is that TAINT_* will effectevely become part of kernel ABI > and I'm not sure it's good idea. Taint bits have associated letters: for example panic_on_taint=OP panic on out-of-tree or propriate =) > > Oopsing on any taint will have limited usefulness, I think. >