summaryrefslogtreecommitdiffstats
path: root/net/ipv4/xfrm4_tunnel.c
diff options
context:
space:
mode:
authorPavel Emelyanov <xemul@openvz.org>2008-01-10 12:48:38 +0100
committerDavid S. Miller <davem@davemloft.net>2008-01-10 12:48:38 +0100
commit9cd40029423701c376391da59d2c6469672b4bed (patch)
treea49624a361ab9c28879efc68862aee819538e9bc /net/ipv4/xfrm4_tunnel.c
parent[NIU]: Support for Marvell PHY (diff)
downloadlinux-9cd40029423701c376391da59d2c6469672b4bed.tar.xz
linux-9cd40029423701c376391da59d2c6469672b4bed.zip
[NEIGH]: Fix race between neigh_parms_release and neightbl_fill_parms
The neightbl_fill_parms() is called under the write-locked tbl->lock and accesses the parms->dev. The negh_parm_release() calls the dev_put(parms->dev) without this lock. This creates a tiny race window on which the parms contains potentially stale dev pointer. To fix this race it's enough to move the dev_put() upper under the tbl->lock, but note, that the parms are held by neighbors and thus can live after the neigh_parms_release() is called, so we still can have a parm with bad dev pointer. I didn't find where the neigh->parms->dev is accessed, but still think that putting the dev is to be done in a place, where the parms are really freed. Am I right with that? Signed-off-by: Pavel Emelyanov <xemul@openvz.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4/xfrm4_tunnel.c')
0 files changed, 0 insertions, 0 deletions