From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: [PATCH] Reporting file descriptors created by pipe and socketpair
Date: Tue, 12 Sep 2006 13:41:55 -0400 [thread overview]
Message-ID: <200609121341.55412.sgrubb@redhat.com> (raw)
In-Reply-To: <20060912162104.GK4144@devserv.devel.redhat.com>
On Tuesday 12 September 2006 12:21, Alexander Viro wrote:
> c) just how do you propose to do "tracking file descriptors"? It's
> so trivial to confuse that it's not even funny; pass an SCM_RIGHTS
> datagram to yourself and watch that code blow chunks.
So, what would be a good way to let them see the file descriptors created by
these two syscalls? The can get the info for socket, open, accept, ... but
these two are difficult to get at the information.
This might be better as an aux record instead of part of the syscall record
where the field is meaningless for 99.99% of the syscalls.
-Steve
next prev parent reply other threads:[~2006-09-12 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 16:07 [PATCH] Reporting file descriptors created by pipe and socketpair John D. Ramsdell
2006-09-12 16:21 ` Alexander Viro
2006-09-12 17:41 ` Steve Grubb [this message]
2006-09-12 18:25 ` John D. Ramsdell
2006-09-12 19:12 ` Alexander Viro
2006-09-12 21:05 ` John D. Ramsdell
2006-09-12 19:22 ` John D. Ramsdell
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=200609121341.55412.sgrubb@redhat.com \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.