From: Eric Dumazet <eric.dumazet@gmail.com>
To: Nikhil Agarwal <hi2nikhil@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
herbert@gondor.apana.org.au, benjamin.thery@bull.net,
davem@davemloft.net, pstaszewski@itcare.pl
Subject: Re: Fwd: Memory exhaust issue with only IPsec policies configured on continuous traffic
Date: Thu, 10 May 2012 07:27:07 +0200 [thread overview]
Message-ID: <1336627627.12504.127.camel@edumazet-glaptop> (raw)
In-Reply-To: <CAETiZ-QvamMJxfGJDK4CiKngELNevmOXnh7M=UGnkH61XrT5dw@mail.gmail.com>
On Thu, 2012-05-10 at 10:53 +0530, Nikhil Agarwal wrote:
> Hi All,
>
> Can you please help on this?
Dont top post please
>
> -----Original Message-----
> From: Agarwal Nikhil-B38457
> Sent: Wednesday, May 09, 2012 2:53 PM
> To: linux-kernel@vger.kernel.org; netdev@vger.kernel.org
> Subject: Memory exhaust issue with only IPsec policies configured on
> continuous traffic
>
> 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?
Yep, we can use DST_NOCACHE
next prev parent reply other threads:[~2012-05-10 5:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F0B93D0554724543876B9A180DC988575B8867@039-SN1MPN1-001.039d.mgd.msft.net>
[not found] ` <CAETiZ-QTWN2U=hmaCS39Q8hzNysjam+eS5FSi-EYO7cXtTbGKQ@mail.gmail.com>
2012-05-10 5:23 ` Fwd: Memory exhaust issue with only IPsec policies configured on continuous traffic Nikhil Agarwal
2012-05-10 5:27 ` Eric Dumazet [this message]
2012-05-10 5:32 ` Eric Dumazet
2012-05-10 9:42 ` Nikhil Agarwal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1336627627.12504.127.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=benjamin.thery@bull.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=hi2nikhil@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@itcare.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox