Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759077Ab2EIJX0 (ORCPT ); Wed, 9 May 2012 05:23:26 -0400 Received: from va3ehsobe005.messaging.microsoft.com ([216.32.180.31]:35730 "EHLO va3outboundpool.messaging.microsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759056Ab2EIJXY convert rfc822-to-8bit (ORCPT ); Wed, 9 May 2012 05:23:24 -0400 X-Forefront-Antispam-Report: CIP:70.37.183.190;KIP:(null);UIP:(null);IPV:NLI;H:mail.freescale.net;RD:none;EFVD:NLI X-SpamScore: 0 X-BigFish: VS0(zz14ffIzz1202hzzz2dh2a8h668h839h8e2h8e3hd25hbe9i) From: Agarwal Nikhil-B38457 To: "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" Subject: Memory exhaust issue with only IPsec policies configured on continuous traffic Thread-Topic: Memory exhaust issue with only IPsec policies configured on continuous traffic Thread-Index: Ac0tv28IM+yv7QjhQam8Yx0e57jygwAAbzFQAABj4VAAAAsIEAAAmXmA Date: Wed, 9 May 2012 09:23:16 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.232.134.142] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-OriginatorOrg: freescale.com Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1053 Lines: 18 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/