mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Anderson <anderson@redhat.com>
To: Greg KH <gregkh@suse.de>
Cc: CAI Qian <caiqian@redhat.com>,
	tj@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>,
	Guenter Roeck <guenter.roeck@ericsson.com>
Subject: Re: crash failure with 2.6.36-rc3 vmcore
Date: Tue, 7 Sep 2010 09:35:57 -0400 (EDT)	[thread overview]
Message-ID: <1317667916.1487751283866557110.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com> (raw)
In-Reply-To: <471005677.1486991283866304732.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>


----- "Greg KH" <gregkh@suse.de> wrote:

> On Sat, Sep 04, 2010 at 10:06:25PM -0700, Guenter Roeck wrote:
> > I browsed through the code a bit. Looks like the module owner will need to make
> > the necessary changes. The code now seems to depend on kernel internal structure
> > elements. Not sure if that is a good idea in the first place. At least for
> > the attribute owner it will have to be changed to not depend on its existence.
> > 
> > Of course, one could also argue that the field should be re-introduced in 
> > the kernel to make the utility work w/o changes. However, I don't think it
> > would be a good idea to hold the kernel hostage for such problems.
> 
> You're kidding, right?  You should have tools flexable to handle the
> fact that the internal kernel structures change all the time like
> this.  If not, your tools are broken.

Greg,

You are exactly right -- I am the owner/maintainer of the crash utility,
and kernel changes such as this require changes to the tool all the time.

This whole thread should never have been brought up on this list, but I've
been away for a few days, and was unable to nip it in the bud.  It should
have been restricted to the crash-utility@redhat.com mailing list.

Sorry for all the noise...

Dave Anderson  
 


       reply	other threads:[~2010-09-07 13:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <471005677.1486991283866304732.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
2010-09-07 13:35 ` Dave Anderson [this message]
     [not found] <837631540.119231283612666731.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-09-04 15:07 ` caiqian
2010-09-04 17:55   ` Guenter Roeck
2010-09-05  3:17     ` CAI Qian
2010-09-05  5:06       ` Guenter Roeck
2010-09-05  6:22         ` Greg KH
     [not found] <856089343.1931201283439399228.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-09-04  6:01 ` CAI Qian
2010-09-04 14:20   ` Greg KH
2010-09-04 14:43   ` Guenter Roeck

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=1317667916.1487751283866557110.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com \
    --to=anderson@redhat.com \
    --cc=caiqian@redhat.com \
    --cc=gregkh@suse.de \
    --cc=guenter.roeck@ericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    /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®