All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com>
To: kexec@lists.infradead.org
Cc: kumagai-atsushi@mxc.nes.nec.co.jp
Subject: [PATCH 01/10] Scrub executable name for each user process
Date: Thu, 27 Feb 2014 12:01:05 +0530	[thread overview]
Message-ID: <20140227063105.5924.88321.stgit@aruna-ThinkPad-T420> (raw)
In-Reply-To: <20140227063007.5924.5819.stgit@aruna-ThinkPad-T420>

Walk all processes via the tasks lists starting from init_task

   extern struct task_struct init_task;

   struct task_struct {
        ...
        struct list_head tasks;
        ...
        char comm[TASK_COMM_LEN]; /* executable name excluding path */
        ...
   };

For each user space process clear executable name

   struct task_struct *tsk;
   list_for_each_entry(tsk, &init_task, tasks) {
       if (tsk->mm)
           memset(tsk->comm, 0, TASK_COMM_LEN);
   }


Signed-off-by: Aruna Balakrishnaiah <aruna@linux.vnet.ibm.com>
---
 eppic_scripts/proc_names.c |   49 ++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 49 insertions(+)
 create mode 100644 eppic_scripts/proc_names.c

diff --git a/eppic_scripts/proc_names.c b/eppic_scripts/proc_names.c
new file mode 100644
index 0000000..12876df
--- /dev/null
+++ b/eppic_scripts/proc_names.c
@@ -0,0 +1,49 @@
+string
+proc_opt()
+{
+	    return "l";
+}
+
+string
+proc_usage()
+{
+	    return "\n";
+}
+
+static void
+proc_showusage()
+{
+	    printf("usage : proc %s", proc_usage());
+}
+
+string
+proc_help()
+{
+	    return "Help";
+}
+
+int
+proc()
+{
+	struct list_head *head, *next;
+	struct task_struct *tsk;
+
+	tsk = &init_task;
+
+	head = (struct list_head *) &(tsk->tasks);
+	next = (struct list_head *) tsk->tasks.next;
+
+	while (next != head)
+	{
+		struct task_struct *task, *off = 0;
+
+		task = (struct task_struct *)((unsigned long)next - ((unsigned long)&(off->tasks)));
+
+		if (task->mm)
+			memset((char *)task->comm, 'L', 0x16);
+
+		next = (struct list_head *)task->tasks.next;
+	}
+
+	return 1;
+}


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

  reply	other threads:[~2014-02-27  6:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27  6:31 [PATCH 00/10] makedumpfile/eppic: Sample eppic scripts Aruna Balakrishnaiah
2014-02-27  6:31 ` Aruna Balakrishnaiah [this message]
2014-02-27  6:31 ` [PATCH 02/10] Scrub filenames of cached dentries Aruna Balakrishnaiah
2014-02-27  6:31 ` [PATCH 03/10] Scrub all entries in the keyring Aruna Balakrishnaiah
2014-02-27  6:31 ` [PATCH 04/10] Clear the message data of all ap_bus requests Aruna Balakrishnaiah
2014-02-27  6:31 ` [PATCH 05/10] Scrub data in tcp socket buffers Aruna Balakrishnaiah
2014-02-27  6:31 ` [PATCH 06/10] Scrub data of udp " Aruna Balakrishnaiah
2014-02-27  6:31 ` [PATCH 07/10] Scrub data of unix " Aruna Balakrishnaiah
2014-02-27  6:31 ` [PATCH 08/10] Scrub socket buffers of guest network I/O Aruna Balakrishnaiah
2014-02-27  6:31 ` [PATCH 09/10] Scrub buffers involved in guest block I/O Aruna Balakrishnaiah
2014-02-27  6:32 ` [PATCH 10/10] Install sample eppic scripts Aruna Balakrishnaiah
2014-03-05  4:54   ` Atsushi Kumagai
2014-03-05  4:54 ` [PATCH 00/10] makedumpfile/eppic: Sample " Atsushi Kumagai

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=20140227063105.5924.88321.stgit@aruna-ThinkPad-T420 \
    --to=aruna@linux.vnet.ibm.com \
    --cc=kexec@lists.infradead.org \
    --cc=kumagai-atsushi@mxc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.