On Mon, Nov 23, 2015, at 09:32, Dmitry Vyukov wrote: > On Tue, Nov 10, 2015 at 3:59 AM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote: > > On Tue, Nov 10, 2015 at 02:38:54AM +0000, 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 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. :/ -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
