From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: Atsushi Kumagai <ats-kumagai@wm.jp.nec.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [RFC PATCH 0/4] eppic: Create kernel version compatible scripts
Date: Tue, 27 Dec 2016 12:07:25 +0530 [thread overview]
Message-ID: <ad97a55d-df7e-8491-9fd8-1d6e5eb4fd20@linux.vnet.ibm.com> (raw)
In-Reply-To: <0910DD04CBD6DE4193FCF86B9C00BE9701E8EBE7@BPXM01GP.gisp.nec.co.jp>
On Tuesday 27 December 2016 10:52 AM, Atsushi Kumagai wrote:
Hi Atsushi-San,
>> This patch series creates eppic scripts a for range kernel versions
>> they are compatible with. Eppic scripts directory host sample
>> scripts to scrub sensitive information from the dump file generated
>> using makedumpfile.
>>
>> The initial version of these scripts was based on Fedora 19 kernel.
>> In brief, these scripts rely on hard coded kernel data structure
>> member offsets. Kernel data structures are bound to change in due course
>> and leading to failure when assumptions about the offsets differ.
>>
>> Atsushi-San suggested that, it's better to have different version of
>> eppic scripts, those will be valid for the range of kernel release and
>> their naming convention hinting, of the release they are valid across.
>>
>> The first patch renames the existing eppic script to reflect the kernel
>> release they are compatible with. Following the format:
>> <eppic_script>-<valid from kernel version>_to_<valid until kernel version>.c
>>
>> Rest of three patches creates new eppic scripts to match with the kernel
>> data structures they work with.
> Thank you for reflecting my comments, looks good to me.
> v1.6.1 is ready now, these patches will be merged into v1.6.2.
Thank you for the reviews and picking them. Happy New Year.
--
cheers,
Kamalesh.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2016-12-27 6:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 10:05 [RFC PATCH 0/4] eppic: Create kernel version compatible scripts Kamalesh Babulal
2016-12-21 10:05 ` [RFC PATCH 1/4] eppic: Rename scripts to reflect validity of kernel version Kamalesh Babulal
2016-12-21 10:05 ` [RFC PATCH 2/4] eppic/vhost_net_buffers: Introduce changes for kernel 3.19 Kamalesh Babulal
2016-12-21 10:05 ` [RFC PATCH 3/4] eppic/dir_names: Introduce changes for kernel 3.14 Kamalesh Babulal
2016-12-21 10:05 ` [RFC PATCH 4/4] eppic/keyring: Introduce changes for kernel 4.4 Kamalesh Babulal
2016-12-27 5:22 ` [RFC PATCH 0/4] eppic: Create kernel version compatible scripts Atsushi Kumagai
2016-12-27 6:37 ` Kamalesh Babulal [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=ad97a55d-df7e-8491-9fd8-1d6e5eb4fd20@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=ats-kumagai@wm.jp.nec.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