From: Patrick McHardy <[EMAIL PROTECTED]>
Date: Thu, 08 Sep 2005 23:00:39 +0200
> When an error is returned in some cases xfrm_lookup releases
> the dst_entry and sets the pointer to NULL, in some it doesn't.
> There are multiple dst leaks in users of xfrm_lookup because
> not all take care to release the dst_entry when an error was
> returned. Is there a reason why xfrm_lookup doesn't always
> release the dst_entry?
It's a known bug and even listed on the netdev TODO list
at:
http://vger.kernel.org/~davem/net_todo.html
:-)
-
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
