From: Dave Anderson <anderson@redhat.com>
To: "Discussion list for crash utility usage,
maintenance and development" <crash-utility@redhat.com>
Cc: kexec@lists.infradead.org
Subject: Re: [Crash-utility] crash: struct command can read irrelevant pages.
Date: Mon, 24 Feb 2014 09:59:17 -0500 (EST) [thread overview]
Message-ID: <1890371822.15122719.1393253957343.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <0910DD04CBD6DE4193FCF86B9C00BE971EC432@BPXM01GP.gisp.nec.co.jp>
----- Original Message -----
> >Hello Atsushi,
> >
> >I've committed a SLAB/SLUB kmem_cache-specific fix for this issue:
> >
> > https://github.com/crash-utility/crash/commit/c0b7a74fc13121203810d06d163550436b2d5476
> >
> >which is queued for crash-7.0.6.
>
> Thanks Dave, I made sure that this patch solved my problem.
OK good, thanks.
> >> This is a "known" issue has been discussed on the crash-utility list in the
> >> past, at least with respect to the kmem_cache data structure. But for any random
> >> data structure that has such a construct, I'm not sure what can be done.
>
> I also have no ideas how to solve it, but it seems that it hasn't been a
> practical problem yet. So I think your patch is enough for now.
At least with compressed kdumps, the "crash --zero_excluded" command line option,
or "set zero_excluded on" during runtime, should handle 99% of the cases.
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2014-02-24 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 6:01 crash: struct command can read irrelevant pages Atsushi Kumagai
2014-02-19 14:50 ` [Crash-utility] " Dave Anderson
2014-02-20 20:45 ` Dave Anderson
2014-02-24 5:00 ` Atsushi Kumagai
2014-02-24 14:59 ` Dave Anderson [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=1890371822.15122719.1393253957343.JavaMail.zimbra@redhat.com \
--to=anderson@redhat.com \
--cc=crash-utility@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