From: Vivek Goyal <vgoyal@redhat.com>
To: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
Cc: Ken'ichi Ohmichi <oomichi@mxs.nes.nec.co.jp>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
V Srivatsa <vsrivatsa@in.ibm.com>,
kexec@lists.infradead.org, Dave Anderson <anderson@redhat.com>,
Reinhard <BUENDGEN@de.ibm.com>
Subject: Re: [PATCH v2 0/8] makedumpfile: makedumpfile enhancement to filter out kernel data from vmcore
Date: Tue, 24 May 2011 16:35:42 -0400 [thread overview]
Message-ID: <20110524203542.GH3860@redhat.com> (raw)
In-Reply-To: <20110517195751.12740.97565.stgit@mars.in.ibm.com>
On Wed, May 18, 2011 at 01:29:06AM +0530, Mahesh J Salgaonkar wrote:
> Hi All,
>
> Please find the version 2 of makedumpfile enhancement patchset that introduces
> a data filtering feature which enables makedumpfile to filter out desired kernel
> symbol data and it's members from the specified VMCORE file. The data to be
> filtered out is poisoned with character 'X' (58 in Hex).
>
> This feature will be very useful for the customers who wants to erase the
> customer sensitive data like security keys and other confidential data, in
> DUMPFILE before sending it to support team for analysis.
Mahesh,
Apart from security keys, what are the other examples of data which needs
to be removed?
By erasing the data, you mean you set it to zero? Will it make sense to
poison it with some specific pattern so that if crash or other tool
are looking into it they know it has been posioned and it is not a
case of corruption. This might help if a user erased a symbol which was
required by crash for some analysis etc.
Thanks
Vivek
>
> This feature introduces a filter config file where, using filter commands,
> user can specify desired kernel data symbols and it's members that need to be
> filtered out while creating o/p DUMPFILE. The Syntax for filter commands are
> provided in the makedumpfile.conf(8) man page.
>
> The first 4 patches prepares the base work for filtering framework. The
> patches 5 and 6 implements the generic filtering framework to erase desired
> kernel data. The last two patches implements inclusion of eraseinfo data into
> o/p dumpfile (kdump as well as ELF). The eraseinfo data contains the
> effective lines from configuration files.
>
> I have tested these patches on x86_64 and s390x architecture against RHEL6 GA
> kernel. The feature supports filtering data from ELF as well as
> kdump-compressed formatted dump.
>
> Change in v2:
> - Changes in patch 5 and inclusion of new patches 7 & 8
> - Re-named filter.conf file to makedumpfile.conf and some cleanup work.
> - Introduced last two patches that implements inclusion of eraseinfo data
> into kdump compressed as well as ELF formatted dumpfile.
>
> Please review the patchset and let me know your comments.
>
> Thanks,
> -Mahesh.
> ---
>
> Mahesh Salgaonkar (8):
> makedumpfile: Add '--config' option to specify filter config file.
> makedumpfile: Apply relocation while loading module debuginfo.
> makedumpfile: Load the module symbol data from vmcore.
> makedumpfile: Introduce routines to get type name from debuginfo.
> makedumpfile: Read and process filter commands from config file.
> makedumpfile: Read and process 'for' command from config file.
> makedumpfile: Add erased information in compressed kdump file
> makedumpfile: Add erase information in ELF formatted dumpfile
>
>
> IMPLEMENTATION | 6
> Makefile | 8
> diskdump_mod.h | 2
> makedumpfile.8 | 20
> makedumpfile.c | 2747 ++++++++++++++++++++++++++++++++++++++++++++++++---
> makedumpfile.conf | 149 +++
> makedumpfile.conf.8 | 419 ++++++++
> makedumpfile.h | 199 ++++
> 8 files changed, 3394 insertions(+), 156 deletions(-)
> create mode 100644 makedumpfile.conf
> create mode 100644 makedumpfile.conf.8
>
> --
> Signature
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-05-24 20:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 19:59 [PATCH v2 0/8] makedumpfile: makedumpfile enhancement to filter out kernel data from vmcore Mahesh J Salgaonkar
2011-05-18 0:49 ` Ken'ichi Ohmichi
2011-05-24 20:35 ` Vivek Goyal [this message]
2011-05-24 20:47 ` Dave Anderson
[not found] ` <OF341326C7.0D81F89A-ONC125789B.002DB6ED-C125789B.002FC7A0@de.ibm.com>
2011-05-25 19:53 ` Vivek Goyal
2011-05-26 11:15 ` Reinhard Buendgen
2011-05-26 13:39 ` Vivek Goyal
2011-05-27 6:56 ` Mahesh J Salgaonkar
2011-07-15 5:20 ` Ken'ichi Ohmichi
2011-07-15 7:10 ` Mahesh J Salgaonkar
2011-07-15 7:38 ` Ken'ichi Ohmichi
2011-05-25 7:44 ` Mahesh J Salgaonkar
2011-05-25 18:55 ` Vivek Goyal
2011-05-25 19:16 ` Dave Anderson
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=20110524203542.GH3860@redhat.com \
--to=vgoyal@redhat.com \
--cc=BUENDGEN@de.ibm.com \
--cc=ananth@in.ibm.com \
--cc=anderson@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=oomichi@mxs.nes.nec.co.jp \
--cc=vsrivatsa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.