System calls that return file descriptors

[Dmitry V. Levin]

On Thu, May 22, 2014 at 08:45:44PM +0530, Zubin Mithra wrote:
> I've restructured it a bit more, added in dup* calls, please see commit at
> [1] and sample output at [2].
> 
> [1]
> https://github.com/eQu1NoX/strace/commit/3d471ba8fccc531b8bc33b6467644b2d17ba8cc0
> [2] https://gist.github.com/eQu1NoX/ccd6e2f9d45e2e0e82f9
> 
> > There is a receive call, that allows to forward open file descriptors
> > between
> > processes. I do not known, if you call those received fds "socket fds",
> > since
> > they could be any (unresolvable) fd -- unless you poke into /proc for more
> > information.
> 
> Could you please give more information on which syscall you are referring
> to? I couldn't find a syscall that matched your description.

recvmsg and recvmmsg, decoded using printcmsghdr (see SCM_RIGHTS).
I suppose it should just use printfd.

These syscalls don't return file descriptors, they may receive them from
the kernel in a way more similar to pipe/pipe2/socketpair rather than
open/creat/dup/dup2/dup3.


-- 
ldv
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20140523/fb263141/attachment.bin>