public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Sud <pigsflew2008@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Parsing Structures postmortem from memory dump
Date: Tue, 06 May 2008 15:04:05 -0400	[thread overview]
Message-ID: <4820ABA5.3020705@gmail.com> (raw)

Hi,

I am working on a project attempting to extend the volatility toolkit 
(www.volatilesystems.com) to read Linux memory; for now I am attempting 
to support Kernel 2.6.22-14 using i686 arch.

What I mean to do is have it first identify that the image is from a 
linux environment, and then parse out the processes that were running 
when the image was taken.

I've looked at /include/linux/sched.h and tried to understand the 
task_struct structure, but it appears to be variable-length, determined 
at compile time, and I can't tell exactly how these are stored 
throughout memory--In a list? a tree?

If anyone can point me to more information toward finding out how to 
trace this, I would appreciate it.

Thank you,

Adrian Sud

UMass Amherst
Dept. of Computer Science

             reply	other threads:[~2008-05-06 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 19:04 Adrian Sud [this message]
2008-05-06 22:37 ` Parsing Structures postmortem from memory dump Dan Noé

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=4820ABA5.3020705@gmail.com \
    --to=pigsflew2008@gmail.com \
    --cc=linux-kernel@vger.kernel.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