linux-kernel - Re: interpreting semantics of ipc system call

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 30 Sep 2010 18:04:05 +0800
From:	Américo Wang <xiyou.wangcong@...il.com>
To:	Andreas Saebjoernsen <andreas@...italplaywright.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: interpreting semantics of ipc system call

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'.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/