[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20151027.080434.2260743137698389975.davem@davemloft.net>
Date: Tue, 27 Oct 2015 08:04:34 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: Alan.Burlison@...cle.com
Cc: Casper.Dik@...cle.com, viro@...IV.linux.org.uk,
eric.dumazet@...il.com, 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)
From: Alan Burlison <Alan.Burlison@...cle.com>
Date: Tue, 27 Oct 2015 14:39:56 +0000
> On 27/10/2015 14:39, David Miller wrote:
>
>> Making this worse is that there isn't going to be a straightforward
>> nor reliable way to test for the presence of this at run time.
>
> I attached a test case to the original bug that demonstrates the
> platform-specific behaviours, it would be easy enough to modify that
> to use as a configure-time feature probe.
I said "run time". Like when your final code runs on a target system.
Not at build tree configure time.
--
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