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, LChouinard@s2sys.com,
tachibana@mxm.nes.nec.co.jp, anderson@redhat.com,
vgoyal@redhat.com, buendgen@de.ibm.com
Subject: Re: [PATCH v2 0/7] makedumpfile security key filtering with eppic
Date: Tue, 04 Dec 2012 14:26:11 +0530 [thread overview]
Message-ID: <50BDBAAB.6050207@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121204173625.b79ad10832e0adaa6e4db451@mxc.nes.nec.co.jp>
On 2012-12-04 14:06, Atsushi Kumagai wrote:
> Hello Aravinda,
>
> On Mon, 3 Dec 2012 13:40:01 -0500
> Vivek Goyal <vgoyal@redhat.com> wrote:
>
>> On Mon, Dec 03, 2012 at 08:05:54PM +0530, Aravinda Prasad wrote:
>>
>> [..]
>>>>> Another approach is to dynamically load libeppic library - similar way
>>>>> how crash does it. No major changes will be done to makedumpfile code,
>>>>> except the addition of --eppic flag. Upon specifying --eppic flag
>>>>> makedumpfile will dlopen libeppic.so, which will have functionality to
>>>>> scrub the specified data. This will prevent makedumpfile bloat and will
>>>>> not affect the size of initramfs as --eppic is only specified during
>>>>> post processing. The distribution should build and ship libeppic.so and
>>>>> the procedure for building .so will be similar to what we have in crash.
>>>>
>>>> It will still show up in dynamic library dependencing using ldd. We will
>>>> have to put some hack to exclude the leppic despite the fact that
>>>> makedumpfile is dependent on it.
>>>>
>>>> In F18, now we use dracut to build kdump initramfs. On command line we
>>>> specify any extra binaries to be included and makedumpfile is one of
>>>> those. Dracut will determine all the dependencies and automatically pull
>>>> these in. So even if we don't use --eppic flag, dracult will pull in
>>>> eppic shared library anyway.
>>>
>>>
>>> I think ldd or dracut will not be able to make out that we are dependent
>>> on libeppic.so as we will be using the dlopen("libeppic.so, ...) call to
>>> dynamically load. No extra flags will be added to Makefile to specify
>>> -leppic while building makedumpfile. Hence, from my understanding, while
>>> building kdump initramfs, dracut cannot determine that we are dependent
>>> on eppic
>>
>> Ok, if dracut does not pull in libeppic and does not bloat size of
>> initramfs, I am fine.
>
> I agree with this idea too.
>
> However, the release date is closing in, so would you re-send the patch set
> based on v1.5.1 ? I will accept it as official feature in v1.5.2.
>
sure. Thanks Atsushi
>
> Thanks
> Atsushi Kumagai
>
--
Regards,
Aravinda
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-12-04 8:56 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 13:37 [PATCH v2 0/7] makedumpfile security key filtering with eppic Aravinda Prasad
2012-11-08 13:38 ` [PATCH v2 1/7] Initialize and setup eppic Aravinda Prasad
2012-11-15 16:04 ` Vivek Goyal
2012-11-16 9:43 ` Aravinda Prasad
2012-11-08 13:38 ` [PATCH v2 2/7] makedumpfile and eppic interface layer Aravinda Prasad
2012-11-08 13:38 ` [PATCH v2 3/7] Eppic call back functions to query a dump image Aravinda Prasad
2012-11-08 13:38 ` [PATCH v2 4/7] Implement apigetctype call back function Aravinda Prasad
2012-11-08 13:39 ` [PATCH v2 5/7] Implement apimember and apigetrtype call back functions Aravinda Prasad
2012-11-08 13:39 ` [PATCH v2 6/7] Extend eppic built-in functions to include memset function Aravinda Prasad
2012-11-08 13:39 ` [PATCH v2 7/7] Support fully typed symbol access mode Aravinda Prasad
2012-11-14 1:15 ` [PATCH v2 0/7] makedumpfile security key filtering with eppic Atsushi Kumagai
2012-11-14 14:54 ` Vivek Goyal
2012-11-14 17:06 ` Aravinda Prasad
2012-11-14 17:53 ` Vivek Goyal
2012-11-15 12:50 ` Aravinda Prasad
2012-11-15 14:27 ` Dave Anderson
2012-11-15 15:55 ` Vivek Goyal
2012-11-16 9:52 ` Aravinda Prasad
2012-11-16 14:36 ` Vivek Goyal
2012-11-20 9:47 ` Atsushi Kumagai
2012-11-21 7:19 ` Aravinda Prasad
2012-11-21 13:57 ` Vivek Goyal
2012-11-22 17:14 ` Aravinda Prasad
2012-11-26 14:04 ` Vivek Goyal
2012-12-03 6:02 ` Aravinda Prasad
2012-12-03 13:20 ` Vivek Goyal
2012-12-03 14:35 ` Aravinda Prasad
2012-12-03 18:40 ` Vivek Goyal
2012-12-04 8:36 ` Atsushi Kumagai
2012-12-04 8:56 ` Aravinda Prasad [this message]
2012-12-06 15:26 ` Dave Anderson
2012-12-07 6:05 ` Aravinda Prasad
2012-12-07 13:46 ` Luc Chouinard
2012-12-07 21:59 ` Vivek Goyal
2012-12-10 7:32 ` Aravinda Prasad
2012-12-10 11:35 ` Aravinda Prasad
2012-11-16 9:49 ` Aravinda Prasad
2012-11-15 15:49 ` Vivek Goyal
2012-11-16 11:10 ` Aravinda Prasad
2012-11-16 14:59 ` Vivek Goyal
2012-11-14 20:15 ` Vivek Goyal
2012-11-15 12:55 ` Aravinda Prasad
2012-11-14 20:21 ` Dave Anderson
2012-11-15 13:27 ` Aravinda Prasad
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=50BDBAAB.6050207@linux.vnet.ibm.com \
--to=aravinda@linux.vnet.ibm.com \
--cc=LChouinard@s2sys.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=mahesh@linux.vnet.ibm.com \
--cc=tachibana@mxm.nes.nec.co.jp \
--cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox