public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Walle <bwalle@suse.de>
To: Vivek Goyal <vgoyal@in.ibm.com>
Cc: Dan Aloni <da-x@monatomic.org>,
	"Ken'ichi Ohmichi" <oomichi@mxs.nes.nec.co.jp>,
	Neil Horman <nhorman@redhat.com>,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: Determine version of kernel that produced vmcore
Date: Wed, 11 Jul 2007 10:58:10 +0200	[thread overview]
Message-ID: <20070711085810.GB23466@suse.de> (raw)
In-Reply-To: <20070711060726.GA5310@in.ibm.com>

* Vivek Goyal <vgoyal@in.ibm.com> [2007-07-11 08:07]:
> On Tue, Jul 10, 2007 at 07:52:01PM +0300, Dan Aloni wrote:
> > On Tue, Jul 10, 2007 at 08:09:04AM -0400, Neil Horman wrote:
> > > On Tue, Jul 10, 2007 at 12:18:17PM +0530, Vivek Goyal wrote:
> > > > On Fri, Jul 06, 2007 at 05:58:04PM +0300, Dan Aloni wrote:
> > > > > On Fri, Jul 06, 2007 at 03:28:14PM +0200, Bernhard Walle wrote:
> > > > > > Hello,
> > [...]
> > > > > It contains enough information in order to make a compact kernel
> > > > > dump (makedumpinfo needs to go over the struct page arrays). As
> > > > > you see, it also contains the kernel version.
> > > > > 
> > > > 
> > > > But this will not solve Bernhard's problem where looking at a vmcore
> > > > he wants to know which vmlinux (kernel version with time stamp) has
> > > > generated this vmcore. So adding a ELF NOTE should help.
> > > > 
> > > I think an ELF note would be a fine idea.
> > 
> > Okay, so here's an implemenation.
> > 
> > See the attached proof-of-concept patches to the kernel-side kexec and 
> > kexec-tools (might need some cleanup though). Next to follow, a patch 
> > to makedumpfile. With these patches a new "LINUX" elf note generated 
> > by the kernel in the format that makedumpfile expects and is being 
> > passed on by the kexec util to the kdump kernel.
> > 
> > As a bonus, with this patch you don't even have to compile the kernel 
> > with debug information in order for the filtering to work.
> > 
> 
> This implementation looks interesting. No need of debug compiled
> vmlinux for dump filtering purposes. No run time vmlinux binary modifications
> as suggested by your previous mails. People can export kernel CONFIG info
> like PAGESIZE etc with the help of this ELF note and any tool which is
> processing kernel core file can benifit from this. No guesses required for
> determining the page size of crashed kernel.

I also like way of implementing it. :)


Thanks,
   Bernhard

  parent reply	other threads:[~2007-07-11  8:58 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 13:28 Determine version of kernel that produced vmcore Bernhard Walle
2007-07-06 14:58 ` Dan Aloni
2007-07-09  9:21   ` Bernhard Walle
2007-07-09 11:41     ` Dan Aloni
2007-07-09 20:49       ` Bernhard Walle
2007-07-10  4:45         ` Dan Aloni
2007-07-10 13:20           ` Bernhard Walle
2007-07-10 15:00       ` Vivek Goyal
2007-07-10 17:17         ` Neil Horman
2007-07-10 17:35           ` Dan Aloni
2007-07-10 18:26             ` Dan Aloni
2007-07-10 19:00             ` Neil Horman
2007-07-10 20:36               ` Dan Aloni
2007-07-11 11:57                 ` Neil Horman
2007-07-10  6:48   ` Vivek Goyal
2007-07-10  8:14     ` Dan Aloni
2007-07-10 12:12       ` Neil Horman
2007-07-10 13:05         ` Bernhard Walle
2007-07-10 12:09     ` Neil Horman
2007-07-10 16:52       ` Dan Aloni
2007-07-11  6:07         ` Vivek Goyal
2007-07-11  7:32           ` Dan Aloni
2007-07-11 13:43             ` Ken'ichi Ohmichi
2007-07-13  3:58               ` Vivek Goyal
2007-07-13  7:49                 ` Bernhard Walle
2007-07-13  3:43             ` Vivek Goyal
2007-07-11  8:58           ` Bernhard Walle [this message]
2007-07-10  3:13 ` Ken'ichi Ohmichi
2007-07-10 12:02   ` Neil Horman
2007-07-13 11:05     ` Ken'ichi Ohmichi
2007-07-13 13:15       ` Bernhard Walle
2007-07-16  4:19         ` Vivek Goyal
2007-07-16 11:57           ` Bernhard Walle
2007-07-16 12:25             ` Vivek Goyal
2007-07-16 12:27               ` Bernhard Walle
2007-07-16 12:28               ` Bernhard Walle
2007-07-16 12:36                 ` Vivek Goyal
2007-07-18 14:07                   ` Ken'ichi Ohmichi
2007-07-18 23:10                     ` Bernhard Walle
2007-07-24  6:49                       ` Ken'ichi Ohmichi
2007-07-19 14:12                     ` Vivek Goyal
2007-07-19 16:39                     ` Don Zickus
2007-07-19 16:49                       ` Bernhard Walle
2007-07-19 16:59                         ` Don Zickus
2007-07-23  5:01                       ` Vivek Goyal
2007-07-23 11:47                         ` Ken'ichi Ohmichi
2007-07-23 13:02                           ` Dan Aloni
2007-07-23 15:58                             ` Vivek Goyal
2007-07-24  6:40                             ` Ken'ichi Ohmichi
2007-07-17  3:50             ` Vivek Goyal
2007-07-17  8:17               ` Bernhard Walle
2007-07-10 12:52   ` Bernhard Walle
2007-07-10  6:36 ` Vivek Goyal
2007-07-10 12:59   ` Bernhard Walle

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=20070711085810.GB23466@suse.de \
    --to=bwalle@suse.de \
    --cc=da-x@monatomic.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --cc=oomichi@mxs.nes.nec.co.jp \
    --cc=vgoyal@in.ibm.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