public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, tglx@linutronix.de
Subject: Re: [PATCH] i386: Execute stack overflow warning on interrupt stack
Date: Mon, 05 May 2008 15:47:38 +0200	[thread overview]
Message-ID: <481F0FFA.8060709@firstfloor.org> (raw)
In-Reply-To: <481F0EE1.1000506@sandeen.net>


> We've lost the information about how close we are... that'd be nice to
> keep if possible....

If you don't want to fix it then the message was unnecessary and your
threshold was too high. So you should always fix when you see the
message and the how close information is unnecessary. That is why I
dropped it.

> 
> Can we keep the old printk string and pass the remaining stack in as an arg?

It would have complicated the patch.

-Andi


      reply	other threads:[~2008-05-05 13:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02  9:18 [PATCH] i386: Execute stack overflow warning on interrupt stack Andi Kleen
2008-05-02  9:45 ` Jiri Slaby
2008-05-02  9:48   ` Andi Kleen
2008-05-02  9:45 ` [PATCH] i386: Execute stack overflow warning on interrupt stack II Andi Kleen
2008-05-05  9:59   ` Thomas Gleixner
2008-05-05 10:17     ` Andi Kleen
2008-05-05 12:39       ` Thomas Gleixner
2008-05-05 13:13         ` Eric Sandeen
2008-05-05 13:29         ` Andi Kleen
2008-05-05 13:42           ` Pekka Enberg
2008-05-05 13:45             ` Andi Kleen
2008-05-05 13:42 ` [PATCH] i386: Execute stack overflow warning on interrupt stack Eric Sandeen
2008-05-05 13:47   ` Andi Kleen [this message]

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=481F0FFA.8060709@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=sandeen@sandeen.net \
    --cc=tglx@linutronix.de \
    /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