public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
To: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>
Cc: ananth@in.ibm.com, mahesh@linux.vnet.ibm.com,
	kexec@lists.infradead.org, tachibana@mxm.nes.nec.co.jp,
	lucchouina@yahoo.com, anderson@redhat.com,
	Reinhard Buendgen <buendgen@de.ibm.com>
Subject: Re: Fwd: Re: makedumpfile security key enhancement using SIAL
Date: Tue, 03 Apr 2012 17:03:32 +0530	[thread overview]
Message-ID: <4F7AE00C.1040607@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120330120200.04bcde45.kumagai-atsushi@mxc.nes.nec.co.jp>

Hello Kumagai-san,

On Friday 30 March 2012 08:32 AM, Atsushi Kumagai wrote:
> Hello Aravinda,
>
> On Thu, 22 Mar 2012 22:56:30 +0530
> Aravinda Prasad<aravinda@linux.vnet.ibm.com>  wrote:
>
>> On Wednesday 21 March 2012 12:13 PM, Atsushi Kumagai wrote:
>>> Hello Aravinda,
>>>
>>> I have two questions, could you answer me ?
>>>
>>> First, what problems do you have about the current format of makedumpfile.conf ?
>>
>> Even though makedumpfile.conf is capable of filtering out data from the
>> vmocore, it is not possible to specify and erase complex
>> data-structures. For example it is not possible to traverse a nested
>> list or a tree and then erase a particular node based on some
>> conditions. Extending makedumpfile.conf to support these would require
>> implementing a lot of language constructs. But we can reuse SIAL
>> instead of extending makedumpfile.conf.
>>
>>> Second, what benefits do you expect from using SIAL ? I can't imagine
>>> specific benefits with using SIAL now.
>>
>> SIAL can be used as a language construct to specify rules/commands to
>> erase data in the image file. The makedumpfile would interpret the
>> rules/commands provided by SIAL macros with the help of SIAL library
>> and would suitably erase the required data in the dump file. As SIAL
>> provides a lot of language constructs like conditional statements,
>> logical and arithmetic operators, nested loops, functions etc, it would
>> be possible to traverse nested lists and trees and conditionally erase
>> data in the dump file, enabling users to literally erase any data in
>> the dump file.
>
> Thank you for your explanation.
> It seems good to specify rules with SIAL.
>
> If makedumpfile uses SIAL library, I will discard the current format of
> makedumpfile.conf to reduce the size of source code.
> What do you think about it ?
>

I will come up with a prototype for integrating SIAL with makedumpfile
and then we can discuss whether to discard the existing
makedumpfile.conf format or not. Because the planned makedumpfile
enhancement with SIAL could use some infrastructure provided by
existing implementation like code to erase data in dump file and also
the makedumpfile.conf file can be used to specify SIAL macros.

Regards,
Aravinda

>
> Thanks
> Atsushi Kumagai
>


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

      reply	other threads:[~2012-04-03 11:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4F6870DD.6060102@linux.vnet.ibm.com>
2012-03-21  6:43 ` Fwd: Re: makedumpfile security key enhancement using SIAL Atsushi Kumagai
2012-03-22 17:26   ` Aravinda Prasad
2012-03-30  3:02     ` Atsushi Kumagai
2012-04-03 11:33       ` Aravinda Prasad [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=4F7AE00C.1040607@linux.vnet.ibm.com \
    --to=aravinda@linux.vnet.ibm.com \
    --cc=ananth@in.ibm.com \
    --cc=anderson@redhat.com \
    --cc=buendgen@de.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.nes.nec.co.jp \
    --cc=lucchouina@yahoo.com \
    --cc=mahesh@linux.vnet.ibm.com \
    --cc=tachibana@mxm.nes.nec.co.jp \
    /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