Re: Deadlock in the routing code

2007-12-20 Thread Julian Elischer
Sergey Matveychuk wrote: Julian Elischer wrote: Would this also be a problem that could occur using quagga with zebra and ospfd? Sure, if they use routing sockets. Of course, they are do. then the answer is yes :-) ___ freebsd-net@freebs

Re: Deadlock in the routing code

2007-12-20 Thread Sergey Matveychuk
Julian Elischer wrote: Would this also be a problem that could occur using quagga with zebra and ospfd? Sure, if they use routing sockets. Of course, they are do. -- Dixi. Sem. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/ma

Re: Deadlock in the routing code

2007-12-19 Thread Julian Elischer
Stephen Clark wrote: Julian Elischer wrote: Maxime Henrion wrote: It appears that this patch fixed the problem. My gateway server now has a nearly two days uptime, whereas previously it would have probably crashed already. I'm attaching the final version of the patch here, since the last o

Re: Deadlock in the routing code

2007-12-19 Thread Stephen Clark
Julian Elischer wrote: Maxime Henrion wrote: It appears that this patch fixed the problem. My gateway server now has a nearly two days uptime, whereas previously it would have probably crashed already. I'm attaching the final version of the patch here, since the last one had build-time erro

Re: Deadlock in the routing code

2007-12-19 Thread Julian Elischer
Maxime Henrion wrote: It appears that this patch fixed the problem. My gateway server now has a nearly two days uptime, whereas previously it would have probably crashed already. I'm attaching the final version of the patch here, since the last one had build-time errors. I'm going to commit

Re: Deadlock in the routing code

2007-12-19 Thread Maxime Henrion
Maxime Henrion wrote: > Julian Elischer wrote: > > Gleb Smirnoff wrote: > > >On Thu, Dec 13, 2007 at 10:33:25AM -0800, Julian Elischer wrote: > > >J> Maxime Henrion wrote: > > >J> > Replying to myself on this one, sorry about that. > > >J> > I said in my previous mail that I didn't know yet what p

Re: Deadlock in the routing code

2007-12-17 Thread Julian Elischer
Maxime Henrion wrote: Julian Elischer wrote: Gleb Smirnoff wrote: On Thu, Dec 13, 2007 at 10:33:25AM -0800, Julian Elischer wrote: J> Maxime Henrion wrote: J> > Replying to myself on this one, sorry about that. J> > I said in my previous mail that I didn't know yet what process was J> > holdin

Re: Deadlock in the routing code

2007-12-17 Thread Maxime Henrion
Julian Elischer wrote: > Gleb Smirnoff wrote: > >On Thu, Dec 13, 2007 at 10:33:25AM -0800, Julian Elischer wrote: > >J> Maxime Henrion wrote: > >J> > Replying to myself on this one, sorry about that. > >J> > I said in my previous mail that I didn't know yet what process was > >J> > holding the loc

Re: Deadlock in the routing code

2007-12-14 Thread Julian Elischer
Gleb Smirnoff wrote: On Thu, Dec 13, 2007 at 10:33:25AM -0800, Julian Elischer wrote: J> Maxime Henrion wrote: J> > Replying to myself on this one, sorry about that. J> > I said in my previous mail that I didn't know yet what process was J> > holding the lock of the rtentry that the routed proce

Re: Deadlock in the routing code

2007-12-14 Thread Maxime Henrion
Stephen Clark wrote: > Maxime Henrion wrote: > > >Replying to myself on this one, sorry about that. > > > >I said in my previous mail that I didn't know yet what process was > >holding the lock of the rtentry that the routed process is dealing > >with in rt_setgate(), and I just could verify that

Re: Deadlock in the routing code

2007-12-14 Thread Maxime Henrion
Gleb Smirnoff wrote: > On Thu, Dec 13, 2007 at 10:33:25AM -0800, Julian Elischer wrote: > J> Maxime Henrion wrote: > J> > Replying to myself on this one, sorry about that. > J> > I said in my previous mail that I didn't know yet what process was > J> > holding the lock of the rtentry that the rout

Re: Deadlock in the routing code

2007-12-14 Thread Gleb Smirnoff
On Thu, Dec 13, 2007 at 10:33:25AM -0800, Julian Elischer wrote: J> Maxime Henrion wrote: J> > Replying to myself on this one, sorry about that. J> > I said in my previous mail that I didn't know yet what process was J> > holding the lock of the rtentry that the routed process is dealing J> > with

Re: Deadlock in the routing code

2007-12-13 Thread Julian Elischer
Maxime Henrion wrote: Replying to myself on this one, sorry about that. I said in my previous mail that I didn't know yet what process was holding the lock of the rtentry that the routed process is dealing with in rt_setgate(), and I just could verify that it is held by the swi1: net thread. So

Re: Deadlock in the routing code

2007-12-13 Thread Stephen Clark
Maxime Henrion wrote: Replying to myself on this one, sorry about that. I said in my previous mail that I didn't know yet what process was holding the lock of the rtentry that the routed process is dealing with in rt_setgate(), and I just could verify that it is held by the swi1: net thread. S