[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <DB7PR04MB462082BD6A5587F6E4FB66DF8B4A0@DB7PR04MB4620.eurprd04.prod.outlook.com>
Date: Mon, 25 Nov 2019 09:27:22 +0000
From: Vakul Garg <vakul.garg@....com>
To: Steffen Klassert <steffen.klassert@...unet.com>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: Required guidance to debug ipsec memory leak
> -----Original Message-----
> From: netdev-owner@...r.kernel.org <netdev-owner@...r.kernel.org>
> On Behalf Of Steffen Klassert
> Sent: Monday, November 18, 2019 12:47 PM
> To: Vakul Garg <vakul.garg@....com>
> Cc: netdev@...r.kernel.org
> Subject: Re: Required guidance to debug ipsec memory leak
>
> On Mon, Nov 18, 2019 at 06:35:24AM +0000, Vakul Garg wrote:
> > Hi
> >
> > I need help to debug a suspected memory leak problem while running
> kernel ipsec with rekeying enabled.
>
> Did you try with the current net tree? There is a fix for such a leak:
>
> commit 86c6739eda7d ("xfrm: Fix memleak on xfrm state destroy")
Sorry for a late response. Thanks for the help.
The given patch has helped in reducing the rate at which memory is leaking.
But we are still losing memory at rate of about 30-40MB per hour.
Any pointers in debugging would greatly help.
Powered by blists - more mailing lists