Re: Deadlock between bind and splice

2015-11-23 Thread Hannes Frederic Sowa
On Mon, Nov 23, 2015, at 09:32, Dmitry Vyukov wrote: > On Tue, Nov 10, 2015 at 3:59 AM, Al Viro wrote: > > On Tue, Nov 10, 2015 at 02:38:54AM +, Al Viro wrote: > >> On Fri, Nov 06, 2015 at 07:42:15AM -0800, Eric Dumazet wrote: > >> > >> > Thank you for this report. > >> > > >> > pipe is part o

Re: Deadlock between bind and splice

2015-11-23 Thread Dmitry Vyukov
On Tue, Nov 10, 2015 at 3:59 AM, Al Viro wrote: > On Tue, Nov 10, 2015 at 02:38:54AM +, Al Viro wrote: >> On Fri, Nov 06, 2015 at 07:42:15AM -0800, Eric Dumazet wrote: >> >> > Thank you for this report. >> > >> > pipe is part of fs, not net ;) >> >> AF_UNIX bind() vs. socketpair() interplay, O

Re: Deadlock between bind and splice

2015-11-09 Thread Al Viro
On Tue, Nov 10, 2015 at 02:38:54AM +, Al Viro wrote: > On Fri, Nov 06, 2015 at 07:42:15AM -0800, Eric Dumazet wrote: > > > 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 durat

Re: Deadlock between bind and splice

2015-11-09 Thread Al Viro
On Fri, Nov 06, 2015 at 07:42:15AM -0800, Eric Dumazet wrote: > Thank you for this report. > > pipe is part of fs, not net ;) AF_UNIX bind() vs. socketpair() interplay, OTOH... -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.

Re: Deadlock between bind and splice

2015-11-09 Thread Al Viro
On Fri, Nov 06, 2015 at 01:58:27PM +0100, Dmitry Vyukov wrote: > Hello, > > I am on revision d1e41ff11941784f469f17795a4d9425c2eb4b7a (Nov 5) and > seeing the following lockdep reports. I don't have exact reproducer > program as it is caused by several independent programs (state > accumulated in

Re: Deadlock between bind and splice

2015-11-06 Thread Eric Dumazet
On Fri, 2015-11-06 at 13:58 +0100, Dmitry Vyukov wrote: > Hello, > > I am on revision d1e41ff11941784f469f17795a4d9425c2eb4b7a (Nov 5) and > seeing the following lockdep reports. I don't have exact reproducer > program as it is caused by several independent programs (state > accumulated in kernel

Deadlock between bind and splice

2015-11-06 Thread Dmitry Vyukov
Hello, I am on revision d1e41ff11941784f469f17795a4d9425c2eb4b7a (Nov 5) and seeing the following lockdep reports. I don't have exact reproducer program as it is caused by several independent programs (state accumulated in kernel across invocations); if the report is not enough I can try to cook a