netdev - Re: [Bug 106241] New: shutdown(3)/close(3) behaviour is incorrect for sockets in accept(3)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20151020.042419.299487241092379193.davem@davemloft.net>
Date:	Tue, 20 Oct 2015 04:24:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	Alan.Burlison@...cle.com
Cc:	eric.dumazet@...il.com, stephen@...workplumber.org,
	netdev@...r.kernel.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, 20 Oct 2015 10:59:46 +0100

> The bug goes into quite some detail about how Solaris behaves. The
> issue here is that we have two implementations, Linux and Solaris,
> both claiming to be POSIX-conformant but both showing different
> behaviour. There's a discussion to be had about the whys and
> wherefores of that difference, but saying that you don't want to know
> how Solaris behaves isn't really going to help move the conversation
> along.

With two decades of precendence, applications will need to find a way
to cope with the behavior on every existing Linux kernel out there.

Even if we were to propose something here and change things, it won't
be available on real sites for 6 months at a minimum, and only a an
extremely small fraction of actual machines.

It's more practical for userspace to cope with the bahvior.  This is
simply because coping with current behavior will work on every Linux
kernel on the planet, and also it won't require us to potentially
break any existing setups.

This to me matters more than any squabbling over semantics or who
really implements POSIX correctly or not.  That simply does not matter
at all.

It especially does not matter as far as I and millions of existing
socket apps out there are concerned.
--
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