From: "Ilpo_Järvinen" <ilpo.jarvinen@helsinki.fi> Date: Wed, 4 Jun 2008 02:22:16 +0300 (EEST)I took a close look at this, it seems this patch adds an ABBA deadlock. But I might be wrong. Normally the locking order is: listen_sk --> some_child_sk And this can be seen by the code paths that flow down to tcp_child_process() in net/ipv4/tcp_minisocks.c (via tcp_v4_do_rcv() for example). However here in this patch we will lock in the: child_sk --> listen_sk order. Unless... these defer accepted sockets live outside of the normal socket collection found by tcp_v{4,6}_hnd_req(). If that is the case, that ought to make this locking order OK but I fear that lockdep will likely complain because it has no way to see this distinction. If we cannot find a simple and easy way to deal with this locking problem, I am reverting the defer-accept changes entirely. It's not the end of the world if this feature has to be deferred to 2.6.27 and this bug has been known for several weeks already. --
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Andrew Morton | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Greg KH | Re: [AppArmor 39/45] AppArmor: Profile loading and manipulation, pathname matching |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Arjan van de Ven | Re: [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jarek Poplawski | Re: [BUG] New Kernel Bugs |
