public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Dave Anderson <anderson@redhat.com>
To: kexec@lists.infradead.org
Subject: Re: makedumpfile --dump-dmesg option broken on 3.5 kernels and later
Date: Wed, 30 Jan 2013 12:11:50 -0500 (EST)	[thread overview]
Message-ID: <184157494.18614364.1359565910010.JavaMail.root@redhat.com> (raw)
In-Reply-To: <mailman.13964.1359561994.1038.kexec@lists.infradead.org>



----- Original Message -----
>  Bouchard Louis <louis.bouchard@canonical.com> wrote:
> 
> I now have what looks like a working patch for this issue. Thank to Dave
> Anderson (crash) and Eric Biederman (vmcore-dmesg) for having chewed
> most of the work for me.
> 
> My only remaining problem is to be able to print the syslog level as is
> provided in the previous version.  Currently, the kernel doesn't export
> the 'level:3' offset of the log structure in the vmcoreinfo information
> provided in the vmcore.
> 
> Vivek who authored the original kernel/printk.c patch might be able to
> suggest a better way to expose log.level:3 (I did try to patch the
> kernel but got thrown away because of the nature of .level:3 that didn't
> fit the VMCOREINFO_OFFSET macro)
> 
> In the meantime, I only found this kinda ugly hack to work around the
> absence of the structure element :
> 
> >                 /*
> >                  * Ugly hack around absence of log.level:3
> >                  * Hard code log.level offset = log.dict_len + 3
> >                  */
> >                 level = (UCHAR(logptr + OFFSET(log.dict_len)+3)&level_mask);
> >
> >         sprintf(buf,"<%d>[%5lld.%06ld] ",level,nanos,rem/1000);
> 
> Aside from that, I get an identical dmesg output on kernel 3.5 and after.
> 
> I would appreciate comments on the following before I send the patch to
> the list.

IMHO, just drop it.

As I mentioned on the crash-utility list, it's a PITA keeping up with 
the log structure changes, especially when it involves bit-fields.
The vmcore-dmesg facility just ignores displaying the message evel. 
And for the next crash release, I'm putting the finishing touches on 
a new "crash --log vmcore" option (i.e., without requiring the vmlinux
file), and I'm also going to ignore the log-level.

I understand that "makedumpfile --dump-dmesg" and vmcore-dmesg show
the log level for the legacy log buffer dumps, but that's because
they're embedded in the messages themselves. 

Dave

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

       reply	other threads:[~2013-01-30 17:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.13964.1359561994.1038.kexec@lists.infradead.org>
2013-01-30 17:11 ` Dave Anderson [this message]
2013-01-22 13:52 makedumpfile --dump-dmesg option broken on 3.5 kernels and later Bouchard Louis
2013-01-23  1:19 ` Atsushi Kumagai
2013-01-23  8:49   ` Bouchard Louis
2013-01-30 13:45   ` Bouchard Louis

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=184157494.18614364.1359565910010.JavaMail.root@redhat.com \
    --to=anderson@redhat.com \
    --cc=kexec@lists.infradead.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