From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: kexec@lists.infradead.org
Cc: Atsushi Kumagai <ats-kumagai@wm.jp.nec.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: [RFC PATCH 0/4] eppic: Create kernel version compatible scripts
Date: Wed, 21 Dec 2016 15:35:41 +0530 [thread overview]
Message-ID: <1482314745-5827-1-git-send-email-kamalesh@linux.vnet.ibm.com> (raw)
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.
Kamalesh Babulal (4):
eppic: Rename scripts to reflect validity of kernel version
eppic/vhost_net_buffers: Introduce changes for kernel 3.19
eppic/dir_names: Introduce changes for kernel 3.14
eppic/keyring: Introduce changes for kernel 4.4
eppic_scripts/README | 26 +-
eppic_scripts/ap_messages.c | 82 ------
eppic_scripts/ap_messages_3_10_to_4_8.c | 82 ++++++
eppic_scripts/dir_names.c | 78 -----
eppic_scripts/dir_names_3_10_to_3_13.c | 78 +++++
eppic_scripts/dir_names_3_14_to_4_8.c | 82 ++++++
eppic_scripts/keyring.c | 57 ----
eppic_scripts/keyring_3_10_to_4_3.c | 57 ++++
eppic_scripts/keyring_4_4_to_4_8.c | 378 +++++++++++++++++++++++++
eppic_scripts/proc_names.c | 49 ----
eppic_scripts/proc_names_3_10_to_4_8.c | 49 ++++
eppic_scripts/tcp_sk_buf.c | 82 ------
eppic_scripts/tcp_sk_buf_3_10_to_4_8.c | 82 ++++++
eppic_scripts/udp_sk_buf.c | 83 ------
eppic_scripts/udp_sk_buf_3_10_to_4_8.c | 83 ++++++
eppic_scripts/unix_sk_buff.c | 85 ------
eppic_scripts/unix_sk_buff_3_10_to_4_8.c | 85 ++++++
eppic_scripts/vhost_net_buffers.c | 99 -------
eppic_scripts/vhost_net_buffers_3_10_to_3_18.c | 99 +++++++
eppic_scripts/vhost_net_buffers_3_19_to_4_8.c | 104 +++++++
eppic_scripts/vhost_scsi_buffers.c | 75 -----
eppic_scripts/vhost_scsi_buffers_3_10_to_4_8.c | 75 +++++
22 files changed, 1270 insertions(+), 700 deletions(-)
delete mode 100644 eppic_scripts/ap_messages.c
create mode 100644 eppic_scripts/ap_messages_3_10_to_4_8.c
delete mode 100644 eppic_scripts/dir_names.c
create mode 100644 eppic_scripts/dir_names_3_10_to_3_13.c
create mode 100644 eppic_scripts/dir_names_3_14_to_4_8.c
delete mode 100644 eppic_scripts/keyring.c
create mode 100644 eppic_scripts/keyring_3_10_to_4_3.c
create mode 100644 eppic_scripts/keyring_4_4_to_4_8.c
delete mode 100644 eppic_scripts/proc_names.c
create mode 100644 eppic_scripts/proc_names_3_10_to_4_8.c
delete mode 100644 eppic_scripts/tcp_sk_buf.c
create mode 100644 eppic_scripts/tcp_sk_buf_3_10_to_4_8.c
delete mode 100644 eppic_scripts/udp_sk_buf.c
create mode 100644 eppic_scripts/udp_sk_buf_3_10_to_4_8.c
delete mode 100644 eppic_scripts/unix_sk_buff.c
create mode 100644 eppic_scripts/unix_sk_buff_3_10_to_4_8.c
delete mode 100644 eppic_scripts/vhost_net_buffers.c
create mode 100644 eppic_scripts/vhost_net_buffers_3_10_to_3_18.c
create mode 100644 eppic_scripts/vhost_net_buffers_3_19_to_4_8.c
delete mode 100644 eppic_scripts/vhost_scsi_buffers.c
create mode 100644 eppic_scripts/vhost_scsi_buffers_3_10_to_4_8.c
--
2.7.4
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2016-12-21 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 10:05 Kamalesh Babulal [this message]
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
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=1482314745-5827-1-git-send-email-kamalesh@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