From: Chris J Arges <chris.j.arges@canonical.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-doc@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 3/3] mm: slub: Add SLAB_DEBUG_CRASH option
Date: Fri, 13 Feb 2015 17:52:39 -0600 [thread overview]
Message-ID: <54DE8E47.5040800@canonical.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1502131537430.25326@chino.kir.corp.google.com>
On 02/13/2015 05:38 PM, David Rientjes wrote:
> On Fri, 13 Feb 2015, Chris J Arges wrote:
>
>> This option crashes the kernel whenever corruption is initially detected. This
>> is useful when trying to use crash dump analysis to determine where memory was
>> corrupted.
>>
>> To enable this option use slub_debug=C.
>>
>
> Why isn't this done in other debugging functions such as
> free_debug_processing()?
>
The diff doesn't show this clearly, but the BUG_ON was added to both
free_debug_processing and alloc_debug_processing.
--chris
next prev parent reply other threads:[~2015-02-13 23:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 22:19 [PATCH 1/3] Documentation: minor spelling and grammar fixes Chris J Arges
2015-02-13 22:19 ` [PATCH 2/3] mm: slub: parse slub_debug O option in switch statement Chris J Arges
2015-02-13 23:36 ` David Rientjes
2015-02-13 22:19 ` [PATCH 3/3] mm: slub: Add SLAB_DEBUG_CRASH option Chris J Arges
2015-02-13 23:38 ` David Rientjes
2015-02-13 23:52 ` Chris J Arges [this message]
2015-02-14 0:16 ` Christoph Lameter
2015-02-14 22:32 ` [PATCH v2] " Chris J Arges
2015-02-13 23:58 ` [PATCH 3/3] " Christoph Lameter
2015-02-13 23:12 ` [PATCH 1/3] Documentation: minor spelling and grammar fixes David Rientjes
2015-02-14 0:26 ` Randy Dunlap
2015-02-16 18:58 ` Jonathan Corbet
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=54DE8E47.5040800@canonical.com \
--to=chris.j.arges@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=corbet@lwn.net \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-doc@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®