From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 02F28C3A5A9 for ; Sat, 2 May 2020 23:16:33 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id CD64320787 for ; Sat, 2 May 2020 23:16:32 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org CD64320787 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 6268F8E0005; Sat, 2 May 2020 19:16:32 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5D9358E0001; Sat, 2 May 2020 19:16:32 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4C6D18E0005; Sat, 2 May 2020 19:16:32 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0175.hostedemail.com [216.40.44.175]) by kanga.kvack.org (Postfix) with ESMTP id 3166C8E0001 for ; Sat, 2 May 2020 19:16:32 -0400 (EDT) Received: from smtpin22.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay01.hostedemail.com (Postfix) with ESMTP id E9740180AD806 for ; Sat, 2 May 2020 23:16:31 +0000 (UTC) X-FDA: 76773340182.22.spoon65_39001562f9919 X-HE-Tag: spoon65_39001562f9919 X-Filterd-Recvd-Size: 1731 Received: from gentwo.org (gentwo.org [3.19.106.255]) by imf29.hostedemail.com (Postfix) with ESMTP for ; Sat, 2 May 2020 23:16:31 +0000 (UTC) Received: by gentwo.org (Postfix, from userid 1002) id E5D683EBBD; Sat, 2 May 2020 23:16:30 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by gentwo.org (Postfix) with ESMTP id E4E523EBB9; Sat, 2 May 2020 23:16:30 +0000 (UTC) Date: Sat, 2 May 2020 23:16:30 +0000 (UTC) From: Christopher Lameter X-X-Sender: cl@www.lameter.com To: Rafael Aquini cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, akpm@linux-foundation.org, iamjoonsoo.kim@lge.com, rientjes@google.com, penberg@kernel.org Subject: Re: [PATCH] mm: slub: add panic_on_error to the debug facilities In-Reply-To: <20200501211540.71216-1-aquini@redhat.com> Message-ID: References: <20200501211540.71216-1-aquini@redhat.com> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri, 1 May 2020, Rafael Aquini wrote: > Sometimes it is desirable to override SLUB's debug facilities > default behavior upon stumbling on a cache or object error > and just stop the execution in order to grab a coredump, at > the error-spotting time, instead of trying to fix the issue > and report in an attempt to keep the system rolling. The stopping of execution on an error is the default behavior. Usually you get some OOPS somewhere when data is corrupted and that causes a core dump. SLUB can fix the issue and continue if enabled by specifying special options on boot. That is *not* the default.