[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20180313094939.GN12772@dhcp22.suse.cz>
Date: Tue, 13 Mar 2018 10:49:39 +0100
From: Michal Hocko <mhocko@...nel.org>
To: Gopi Sai Teja <gopi.st@...sung.com>
Cc: "penberg@...nel.org" <penberg@...nel.org>,
"rientjes@...gle.com" <rientjes@...gle.com>,
"iamjoonsoo.kim@....com" <iamjoonsoo.kim@....com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ami Prakash Asthana <prakash.a@...sung.com>,
Lalit Mohan Tripathi <lalit.mohan@...sung.com>,
Himanshu Shukla <himanshu.sh@...sung.com>,
AMIT SAHRAWAT <a.sahrawat@...sung.com>,
PANKAJ MISHRA <pankaj.m@...sung.com>
Subject: Re: Re: Regarding slabinfo tool generating kernel crash
[Sorry for a late reply]
On Thu 01-03-18 12:48:10, Gopi Sai Teja wrote:
> Hi all,
>
> Please find the crash logs attached tested on 4.4.0-116-generic #140-Ubuntu.
> How to reproduce:
>
> Boot the kernel with all slab debug flags enabled(red_zone, poison,
> sanity_checks, store_user)
>
> and run slabinfo -df.
>
> For more info, please check the logs.
> If more info required, please let me know
Slabs are corrupted so you should focus on who causes the corruption.
Please work with your distribution support or try to reproduce with the
current upstream kernel to get more help on the kernel mailing list.
Slabtop merely points out the problem.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists