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: <1445462310.22974.84.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Wed, 21 Oct 2015 14:18:30 -0700
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Casper.Dik@...cle.com
Cc:	David Miller <davem@...emloft.net>, Alan.Burlison@...cle.com,
	viro@...IV.linux.org.uk, 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 Wed, 2015-10-21 at 18:04 +0200, Casper.Dik@...cle.com wrote:

> It is only expensive within the process itself. 

thread synchro would require additional barriers to maintain this state,
for a very unlikely case.

The atomic_{inc|dec}() on file refcount are already a problem.

We certainly do not use/take a lock to find a file pointer into file
descriptor table.

(This lock is only used at open() or close() 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