From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Viro Subject: Re: [PATCH] Reporting file descriptors created by pipe and socketpair Date: Tue, 12 Sep 2006 15:12:25 -0400 Message-ID: <20060912191225.GL4144@devserv.devel.redhat.com> References: <20060912162104.GK4144@devserv.devel.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: "John D. Ramsdell" Cc: bsniffen@mitre.org, Linux Audit List-Id: linux-audit@redhat.com On Tue, Sep 12, 2006 at 02:25:50PM -0400, John D. Ramsdell wrote: > Alexander Viro 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.