Re: [PATCH] mm: trigger panic on bad page or PTE states if panic_on_oops
From: Kirill A. Shutemov
Date: Tue Mar 17 2015 - 15:41:12 EST
On Tue, Mar 17, 2015 at 08:19:19PM +0300, Konstantin Khlebnikov wrote:
> 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=<mask> where <mask> 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 =)
Works for me.
Kirill A. Shutemov
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/