All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Christoph Lameter <cl@linux.com>, Nikolay Borisov <kernel@kyup.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: Wed, 9 Sep 2015 18:26:39 +0200	[thread overview]
Message-ID: <55F05DBF.5050907@suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.11.1509090857170.18992@east.gentwo.org>

On 09/09/2015 04:01 PM, Christoph Lameter wrote:
> On Wed, 9 Sep 2015, Nikolay Borisov wrote:
>
> What does:
>
> 	echo 1 >trace
>
> do? Could crash the sysem due to overload of messages.

Yes I've seen that happen. Did you consider hooking it to trace_printk() 
instead of printk()?

  reply	other threads:[~2015-09-09 16:26 UTC|newest]

Thread overview: 18+ 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-07 11:40   ` Fwd: " Nikolay Borisov
2015-09-08 13:58   ` Christoph Lameter
2015-09-08 14:06     ` Nikolay Borisov
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 [this message]
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=55F05DBF.5050907@suse.cz \
    --to=vbabka@suse.cz \
    --cc=cl@linux.com \
    --cc=kernel@kyup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.