[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151023170900.GX22011@ZenIV.linux.org.uk>
Date: Fri, 23 Oct 2015 18:09:00 +0100
From: Al Viro <viro@...IV.linux.org.uk>
To: Casper.Dik@...cle.com
Cc: Alan Burlison <Alan.Burlison@...cle.com>,
Eric Dumazet <eric.dumazet@...il.com>,
David Miller <davem@...emloft.net>, stephen@...workplumber.org,
netdev@...r.kernel.org, dholland-tech@...bsd.org
Subject: Re: [Bug 106241] New: shutdown(3)/close(3) behaviour is incorrect
for sockets in accept(3)
On Thu, Oct 22, 2015 at 09:50:10PM +0200, Casper.Dik@...cle.com wrote:
> >Sigh... It completely fails to mention descriptor-passing. Which
> > a) is relevant to what "last close" means and
> > b) had been there for nearly the third of a century.
>
> Why is that different? These clearly count as file descriptors.
To quote your own posting upthread (Message-ID:
<201510212033.t9LKX4G8007718@...m101.nl.oracle.com>)
> Well, a file descriptor really only exists in the context of a process;
> in-flight it is no longer a file descriptor as there process context with
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> a file descriptor table; so pointers to file descriptions are passed
> around.
IMO it shows that the wording is anything but clear. The only way to claim
that it's accurate is, indeed, to declare that the contents of in-flight
SCM_RIGHTS datagram should be counted as file descriptors and that's too
much of a stretch for the reasons you've pointed to.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists