* Memory exhaust issue with only IPsec policies configured on continuous traffic
@ 2012-05-09 9:10 Agarwal Nikhil-B38457
2012-05-09 9:23 ` Agarwal Nikhil-B38457
0 siblings, 1 reply; 2+ messages in thread
From: Agarwal Nikhil-B38457 @ 2012-05-09 9:10 UTC (permalink / raw)
To: linux-kernel, linux-crypto, linux-netdev, netdev
Hi all,
In a typical scenario, when IPSEC policies are configured in the system but SA is not present or negotiation fails or IKE daemon is not running. The current behavior of xfrm is to send those matching packets to blackhole route. i.e. xfrm_bundle_lookup returns a bundle with null route and xfrm_lookup returns a blackhole route.
For each of these packet a dst_alloc is called in ipv4_blackhole_route. However when these skbs get free and their dst's get discarded using dst_free and the garbage collector is scheduled using cancel_delayed_work and schedule_delayed_work.
If the packets are coming continuously garbage collector may not get scheduled and large amount of memory is stuck to be freed causing the system to go into non-recoverable state.
Any ideas?
Regards
Nikhil
^ permalink raw reply [flat|nested] 2+ messages in thread
* Memory exhaust issue with only IPsec policies configured on continuous traffic
2012-05-09 9:10 Memory exhaust issue with only IPsec policies configured on continuous traffic Agarwal Nikhil-B38457
@ 2012-05-09 9:23 ` Agarwal Nikhil-B38457
0 siblings, 0 replies; 2+ messages in thread
From: Agarwal Nikhil-B38457 @ 2012-05-09 9:23 UTC (permalink / raw)
To: linux-kernel, netdev
Hi all,
In a typical scenario, when IPSEC policies are configured in the system but SA is not present or negotiation fails or IKE daemon is not running. The current behavior of xfrm is to send those matching packets to blackhole route. i.e. xfrm_bundle_lookup returns a bundle with null route and xfrm_lookup returns a blackhole route.
For each of these packet a dst_alloc is called in ipv4_blackhole_route. However when these skbs get free and their dst's get discarded using dst_free and the garbage collector is scheduled using cancel_delayed_work and schedule_delayed_work.
If the packets are coming continuously garbage collector may not get scheduled and large amount of memory is stuck to be freed causing the system to go into non-recoverable state.
Any ideas?
Regards
Nikhil
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-05-09 9:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-09 9:10 Memory exhaust issue with only IPsec policies configured on continuous traffic Agarwal Nikhil-B38457
2012-05-09 9:23 ` Agarwal Nikhil-B38457
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).