mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: Andreas Saebjoernsen <andreas@digitalplaywright.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: interpreting semantics of ipc system call
Date: Thu, 30 Sep 2010 18:04:05 +0800	[thread overview]
Message-ID: <20100930100405.GB5265@cr0.nay.redhat.com> (raw)
In-Reply-To: <AANLkTik8auzhRB00fRWxbmZKOKg+T87ZZa07ydDAGp=f@mail.gmail.com>

On Wed, Sep 29, 2010 at 03:03:11PM -0700, Andreas Saebjoernsen wrote:
>We are developing a simulator that can simulate any specimen x86 linux program.
>Our simulator has a simulated memory, unlike the concrete memory state of
>tools like Valgrind, so that we can do concrete symbolic execution. Instead of
>reimplementing the system calls we marshal the system calls called by
>the specimen.
>
>I am currently working on marshaling calls to the ipc system call (system
>call 117) which has the following signature
>
>int ipc(unsigned int call, int first, int second, int third, void
>*ptr, long fifth)
>
>I have a problem interpreting what the size is of the data structure
>pointed to by
>the 'void*', and I have been unable to locate good documentation or code on the
>semantics of this system call.


Take a look at ipc/syscall.c, that pointer will be interpreted to different
data structures when you pass different arguments to 'call'.

  parent reply	other threads:[~2010-09-30  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 22:03 Andreas Saebjoernsen
2010-09-29 22:16 ` David Daney
2010-09-30 10:04 ` Américo Wang [this message]
2010-09-30 11:37   ` Arnd Bergmann
2010-09-30 23:29     ` Andreas Saebjoernsen

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=20100930100405.GB5265@cr0.nay.redhat.com \
    --to=xiyou.wangcong@gmail.com \
    --cc=andreas@digitalplaywright.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

all inboxes | Powered by JetHome®