Hi Luc,

Could you please let us know by when you are planning to create the
project and associated git for SIAL? Right now we are extracting
libsial from the crash tar ball and using it.

Regards,
Aravinda

On Wednesday 28 March 2012 10:30 PM, Aravinda Prasad wrote:
Thanks Luc. We will let you know if in case we need any info/help.

I am also forwarding this mail to kexec mailing list.

Regards,
Aravinda


-------- Original Message --------
Subject: RE: Fwd: Re: makedumpfile security key enhancement using SIAL
Date: Wed, 28 Mar 2012 07:07:49 -0400
From: Luc Chouinard <[email protected]>
To: Aravinda Prasad <[email protected]>

Libsial is meant to be a pluggable entity and as such should not require
other pieces to be there ( crash or gdb).
I want to create project and associated git for the library soon. For
now you can extract libsial from the crash tar ball and manage any
modifications using a simple patch mechanism. When the git is available,
we can merge any fixes or enhancements you created for support of
makedumpfile.

Makedumpfile and crash would then feed off of specific branches/versions
of the git repository.
If you have any suggestions or want to help in setting up a public git /
project page for sial, please let me know.


-Luc

-----Original Message-----
From: Aravinda Prasad [mailto:[email protected]]
Sent: Wednesday, March 28, 2012 1:31 AM
To: Luc Chouinard
Subject: Fwd: Fwd: Re: makedumpfile security key enhancement using SIAL

Forwarding to your s2sys email ID. Details in mail forward.

Regards,
Aravinda


-------- Original Message --------
Subject: Fwd: Re: makedumpfile security key enhancement using SIAL
Date: Tue, 20 Mar 2012 17:28:21 +0530
From: Aravinda Prasad <[email protected]>
To: Luc Chouinard <[email protected]>
CC: Atsushi Kumagai <[email protected]>, Masaki Tachibana
<[email protected]>, Mahesh J Salgaonkar
<[email protected]>, Ananth N Mavinakayanahalli
<[email protected]>, Dave Anderson <[email protected]>

Hi Luc,

We are looking for utilising SIAL as a language construct for the
makedumpfile
kernel data filtering from vmcore feature. The details of which are in
the mail
forward.

The proposed enhancement will require libsial.a and as SIAL is not
currently
built/shipped, we are looking for possibilities on how libsial.a can
be made
available to makedumpfile. Please let us know your opinion on the same.

Regards,
Aravinda


-------- Original Message --------
Subject: Re: makedumpfile security key enhancement using SIAL
Date: Tue, 13 Mar 2012 10:27:43 -0400 (EDT)
From: Dave Anderson <[email protected]>
To: Aravinda Prasad <[email protected]>
CC: Atsushi Kumagai <[email protected]>, Masaki
Tachibana <[email protected]>, Ananth N
Mavinakayanahalli <[email protected]>, Mahesh J Salgaonkar
<[email protected]>



----- Original Message -----
> Hi Dave,
>
> Last year, we worked on the makedumpfile security key filtering where
> we added support to filter out kernel data from vmcore. This year, we
> are working on enhancing the framework to provide more flexibility for
> the customers to specify rules to traverse and filter out kernel data
> - for which we are planning to use SIAL.
>
> We are looking into using SIAL as language construct to specify
> rules/commands to erase data in the image file. The makedumpfile would
> interpret the rules provided in SIAL macro using SIAL library (which
> could be dynamically loaded) and erase out suitable data in the vmcore.
> We are planning to reuse SIAL as it provides a C language like
> construct, which is flexible and powerful enough to specify rules to
> erase data in vmcore.
>
> As SIAL is not built and shipped along with crash, we are looking for
> possibilities on how SIAL can be leveraged by makedumpfile and would
> like to know your opinion.

Sorry but I cannot give you any help with SIAL. Luc Chouinard is the
maintainer
of the SIAL extension module adaptation for the crash utility, and he
can answer
your questions w/respect to adapting it for makedumpfile.
And ultimately, that's a question for the makedumpfile maintainers.

Dave



_______________________________________________
kexec mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/kexec

Reply via email to