mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Phil Carmody <ext-phil.2.carmody@nokia.com>
To: ext Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 1/1] sysfs: add more info to the oops dump
Date: Fri, 11 Mar 2011 01:22:28 +0200	[thread overview]
Message-ID: <20110310232228.GI7975@esdhcp04044.research.nokia.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1103110012060.2787@localhost6.localdomain6>

On 11/03/11 00:13 +0100, ext Thomas Gleixner wrote:
> On Fri, 11 Mar 2011, Phil Carmody wrote:
> > On 10/03/11 23:59 +0100, ext Thomas Gleixner wrote:
> > > On Thu, 10 Mar 2011, Andrew Morton wrote:
...
> > > > I don't think it's a terribly useful feature.  Except for when it _is_
> > > > useful, when it's very useful ;) The world wouldn't end if we decided
> > > > to remove it.
> > > 
> > > Amen to that.
> > > 
> > > It's more of an distraction than anything which is relevant to 99.999%
> > > of the problems we have to deal with.
> > 
> > As I indicated before, I've previously thought that too, but thought I
> > could 'fix' it by adding to it when I hit the once-in-three-years case.
> 
> The interesting question is:
> 
>  How did that info help and was it really the ultimate reason why you
>  found the underlying bug ?

It's academic now, as I fully support the removal. Perhaps the information
was most useful simply because it was given to me quickly, there would have
been other ways of divining it certainly (I can read hex stack dumps, for
example). Even I don't need this patch any more!

At least my intrusion has been useful for instigating a little cleanup!

Cheers,
Phil

      parent reply	other threads:[~2011-03-10 23:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 15:53 [PATCH " Phil Carmody
2011-03-10 16:25 ` Greg KH
2011-03-10 18:32   ` Phil Carmody
2011-03-10 19:02     ` Greg KH
2011-03-10 21:10       ` Phil Carmody
2011-03-10 21:27         ` Greg KH
2011-03-10 22:27           ` [PATCHv3 0/1] " Phil Carmody
2011-03-10 22:27             ` [PATCHv3 1/1] " Phil Carmody
2011-03-10 22:38               ` Andrew Morton
2011-03-10 22:59                 ` Thomas Gleixner
2011-03-10 23:03                   ` Greg KH
2011-03-10 23:15                     ` Andrew Morton
2011-03-10 23:06                   ` Phil Carmody
2011-03-10 23:13                     ` Thomas Gleixner
2011-03-10 23:22                       ` Andrew Morton
2011-03-10 23:27                         ` Thomas Gleixner
2011-03-10 23:46                           ` Thomas Gleixner
2011-03-10 23:22                       ` Phil Carmody [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=20110310232228.GI7975@esdhcp04044.research.nokia.com \
    --to=ext-phil.2.carmody@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®