From: Michal Hocko <mhocko@kernel.org>
To: Gopi Sai Teja <gopi.st@samsung.com>
Cc: "penberg@kernel.org" <penberg@kernel.org>,
"rientjes@google.com" <rientjes@google.com>,
"iamjoonsoo.kim@lge.com" <iamjoonsoo.kim@lge.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ami Prakash Asthana <prakash.a@samsung.com>,
Lalit Mohan Tripathi <lalit.mohan@samsung.com>,
Himanshu Shukla <himanshu.sh@samsung.com>,
AMIT SAHRAWAT <a.sahrawat@samsung.com>,
PANKAJ MISHRA <pankaj.m@samsung.com>
Subject: Re: Regarding slabinfo tool generating kernel crash
Date: Tue, 27 Feb 2018 14:55:17 +0100 [thread overview]
Message-ID: <20180227135517.GA29402@dhcp22.suse.cz> (raw)
In-Reply-To: <20180226132235epcms5p2a7d2f362274ffc45198c574057ec82fb@epcms5p2>
On Mon 26-02-18 18:52:35, Gopi Sai Teja wrote:
> Hi all,
>
> We are using slabinfo tool with -df option. Tool is generating kernel crash.
> Please help if anyone got same issue.
>
> Our kernel image was built with poison, store_user, red_zone and sanity_checks
> enabled in slab debug.
Such a report is basically pointless without the crash report and the
kernel version which happens to be affected.
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-27 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180226132235epcms5p2a7d2f362274ffc45198c574057ec82fb@epcms5p2>
2018-02-26 13:22 ` Gopi Sai Teja
2018-02-27 13:55 ` Michal Hocko [this message]
[not found] ` <CGME20180226132235epcms5p2a7d2f362274ffc45198c574057ec82fb@epcms5p1>
2018-03-01 7:18 ` Gopi Sai Teja
2018-03-13 9:49 ` Michal Hocko
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=20180227135517.GA29402@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=a.sahrawat@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=gopi.st@samsung.com \
--cc=himanshu.sh@samsung.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=lalit.mohan@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pankaj.m@samsung.com \
--cc=penberg@kernel.org \
--cc=prakash.a@samsung.com \
--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