On Tue, Feb 26, 2008 at 12:14:26PM +0000, James Chapman wrote: > Jarek Poplawski wrote: >> Jarek Poplawski wrote, On 02/25/2008 02:39 PM: >> ... >>> Hmm... Wait a minute! But on the other hand David has written about >>> his cons here, and it looks reasonable: this place would be fixed, >>> but some others can start reports like this. Maybe, it's better to >>> analyze yet if it's really so hard to eliminate taking this lock >>> on the xmit path? >> >> James, I wonder if you could try to test this patch below? >> ip_queue_xmit() seems to do proper things with __sk_dst_check(), and >> if some other functions don't behave similarly lockdep should tell. >> I think, you could test it with your "locks to _bh" patch (without >> pppol2tp_xmit() part), and maybe with my sock.c lockdep patch (it >> should help lockdep to see these locks a bit more distinctly). > > I found the same thing and was running a variant of your patch last > night; rather than set skb->dst to NULL though, I use __sk_dst_get() and > let ip_queue_xmit() do the route lookup if it returns NULL. But this has > the same symptoms as the code I tried a few days ago - no lockdep errors > but a system lockup after up to several hours. Nothing is logged in the > syslog.
I guess you are going to try this together with this sk_dst_lock with bh patch too. If it's possible I'd suggest to try this skb->dst = NULL as well (__sk_dst_get instead of __sk_dst_check seems to be too racy). > Luckily, I'm in the lab where my two borrowed servers are today so I > have access to their consoles. Hopefully I'll be able to find out why > there are hanging. Btw, they don't hang if I disable irqs around the > ppp_input() call. ...and disabling bh instead isn't enough, BTW? > Will update you later. Thanks, Jarek P. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html