linux-kernel - 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-next>] [day] [month] [year] [list]

Date:	Wed, 29 Sep 2010 15:03:11 -0700
From:	Andreas Saebjoernsen <andreas@...italplaywright.com>
To:	linux-kernel@...r.kernel.org
Subject: interpreting semantics of ipc system call

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.

Could you please help me interpret the size of the data structure
pointed to by the
'void*' or point me to documentation/code for the ipc system call?

kind regards,
Andreas
--
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/