All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rafael Aquini <aquini@redhat.com>
To: Qian Cai <cai@lca.pw>
Cc: Linux-MM <linux-mm@kvack.org>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	iamjoonsoo.kim@lge.com, rientjes@google.com, penberg@kernel.org,
	cl@linux.com
Subject: Re: [PATCH] mm: slub: add panic_on_error to the debug facilities
Date: Sun, 3 May 2020 22:36:43 -0400	[thread overview]
Message-ID: <20200504023643.GA18463@t490s> (raw)
In-Reply-To: <8CD9EA82-8BE1-47B4-AD35-7D300CAD745C@lca.pw>

On Fri, May 01, 2020 at 07:17:24PM -0400, Qian Cai wrote:
> 
> 
> > On May 1, 2020, at 5:54 PM, Rafael Aquini <aquini@redhat.com> wrote:
> > 
> > It seems like a good idea which also would required "adding things"
> > elsewhere, but doesn't look mutually exclusive with the approach here.
> 
> Also, what’s so special about these bad pages here that deserve a crash dump, but not other TAINT_BAD_PAGE places?
>

In that light, yes they're not as different and we could better leverage
a panic_on_taint mechanism (similar to panic_on_warn).

I'll get that posted soon.

Thanks.
-- Rafael 



  reply	other threads:[~2020-05-04  2:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 21:15 [PATCH] mm: slub: add panic_on_error to the debug facilities Rafael Aquini
2020-05-01 21:29 ` Qian Cai
2020-05-01 21:54   ` Rafael Aquini
2020-05-01 22:00     ` Qian Cai
2020-05-01 23:17     ` Qian Cai
2020-05-04  2:36       ` Rafael Aquini [this message]
2020-05-01 21:37 ` Andrew Morton
2020-05-01 21:41   ` Rafael Aquini
2020-05-02 23:16 ` Christopher Lameter
2020-05-04  2:51   ` Rafael Aquini
2020-05-08  3:06     ` Christopher Lameter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200504023643.GA18463@t490s \
    --to=aquini@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=cai@lca.pw \
    --cc=cl@linux.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.