Thread (7 messages) read the whole thread 7 messages, 4 authors, 2015-11-23

Re: Deadlock between bind and splice

From: Hannes Frederic Sowa <hidden>
Date: 2015-11-23 09:21:27
Also in: linux-fsdevel, lkml

On Mon, Nov 23, 2015, at 09:32, Dmitry Vyukov wrote:
On Tue, Nov 10, 2015 at 3:59 AM, Al Viro [off-list ref] wrote:
quoted
On Tue, Nov 10, 2015 at 02:38:54AM +0000, Al Viro wrote:
quoted
On Fri, Nov 06, 2015 at 07:42:15AM -0800, Eric Dumazet wrote:
quoted
Thank you for this report.

pipe is part of fs, not net ;)
AF_UNIX bind() vs. socketpair() interplay, OTOH...
FWIW, BSD folks unlock the socket for the duration of mknod - mark it as
"somebody's trying to bind it" to avoid the fun with racing double bind(),
but that's about it.  Tempting, to be honest...

BTW, why does unix_autobind() do allocation under ->readlock?  The allocation
will be normally used - that if (u->addr) return; part is just dealing with
an unlikely race, as far as I can see...

Hello,

This is still happening periodically for me. Is there a proposed fix?
I could test it.
No, we currently have no fix for that report. :/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help