Linux-audit Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Viro <aviro@redhat.com>
To: "John D. Ramsdell" <ramsdell@mitre.org>
Cc: bsniffen@mitre.org, Linux Audit <linux-audit@redhat.com>
Subject: Re: [PATCH] Reporting file descriptors created by pipe and socketpair
Date: Tue, 12 Sep 2006 15:12:25 -0400	[thread overview]
Message-ID: <20060912191225.GL4144@devserv.devel.redhat.com> (raw)
In-Reply-To: <ogt3baxyma9.fsf@divan.mitre.org>

On Tue, Sep 12, 2006 at 02:25:50PM -0400, John D. Ramsdell wrote:
> Alexander Viro <aviro@redhat.com> writes:
> 
> > c) just how do you propose to do "tracking file descriptors"?
> 
> We aren't proposing to track file descriptors.  We already have code
> that does that

Indeed?  And how, pray tell, do you handle e.g. processes A and B sending
SCM_RIGHTS datagrams to C at the same moment?  With data part containing
the indication which process had sent them, so C can handle them just
fine and do that in different ways depending on the origin of datagram.
Note that looking at the timestamps will not help you at all - you can
get
	A enters sendmsg(2)
	B enters sendmsg(2)
	B puts datagram into queue
	A puts datagram into queue
	A leaves sendmsg(2)
	B leaves sendmsg(2)
quite easily.

  reply	other threads:[~2006-09-12 19:12 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
2006-09-12 18:25   ` John D. Ramsdell
2006-09-12 19:12     ` Alexander Viro [this message]
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=20060912191225.GL4144@devserv.devel.redhat.com \
    --to=aviro@redhat.com \
    --cc=bsniffen@mitre.org \
    --cc=linux-audit@redhat.com \
    --cc=ramsdell@mitre.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