From: Nikolay Borisov <kernel@kyup.com>
To: Christoph Lameter <cl@linux.com>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
Marian Marinov <mm@1h.com>,
SiteGround Operations <operations@siteground.com>
Subject: Re: Kernel 4.1.6 Panic due to slab corruption
Date: Tue, 8 Sep 2015 17:06:39 +0300 [thread overview]
Message-ID: <55EEEB6F.2090302@kyup.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1509080857300.24606@east.gentwo.org>
On 09/08/2015 04:58 PM, Christoph Lameter wrote:
> On Mon, 7 Sep 2015, Nikolay Borisov wrote:
>
>> Did a bit more investigation and it turns out the
>> corruption is happening in slab_alloc_node, in the
>> 'else' branch when get_freepointer is being called:
>
> Please reboot the system and specify
>
> slub_debug
>
Unfortunately I haven't found a way to reproduce it so the only option
would be to do this on a live server. However, the performance impact I
believe is going to be very prohibitive :(. Alternatively what I could
do is probably leave merging on but enable debugging only for the
kmalloc-32 slab cache. Do you think this would provide enough
information to help track the corruption when it happens, without
impacting performance?
> on the kernel command line. This will enable additional diagnostics which
> will allow tracking down the issue to the subsystem causing it.
>
>
> Or rebuild with
>
> CONFIG_SLUB_DEBUG_ON
>
next prev parent reply other threads:[~2015-09-08 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 8:41 Kernel 4.1.6 Panic due to slab corruption Nikolay Borisov
2015-09-07 10:37 ` Holger Hoffstätte
2015-09-07 11:30 ` Nikolay Borisov
2015-09-07 11:49 ` Holger Hoffstätte
2015-09-07 11:58 ` Holger Hoffstätte
2015-09-07 11:14 ` Nikolay Borisov
2015-09-08 13:58 ` Christoph Lameter
2015-09-08 14:06 ` Nikolay Borisov [this message]
2015-09-08 14:27 ` Christoph Lameter
2015-09-08 14:41 ` Nikolay Borisov
2015-09-08 15:15 ` Christoph Lameter
2015-09-09 11:40 ` Nikolay Borisov
2015-09-09 14:01 ` Christoph Lameter
2015-09-09 16:26 ` Vlastimil Babka
2015-09-09 17:58 ` Christoph Lameter
2015-09-10 6:12 ` Nikolay Borisov
2015-09-10 16:30 ` Christoph 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=55EEEB6F.2090302@kyup.com \
--to=kernel@kyup.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm@1h.com \
--cc=operations@siteground.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;
as well as URLs for NNTP newsgroup(s).