[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55EEEB6F.2090302@kyup.com>
Date: Tue, 8 Sep 2015 17:06:39 +0300
From: Nikolay Borisov <kernel@...p.com>
To: Christoph Lameter <cl@...ux.com>
Cc: "Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
Marian Marinov <mm@...com>,
SiteGround Operations <operations@...eground.com>
Subject: Re: Kernel 4.1.6 Panic due to slab corruption
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
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists