From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net] inet: frag: make sure forced eviction removes all frags
Date: Thu, 06 Mar 2014 15:29:35 -0500 (EST) [thread overview]
Message-ID: <20140306.152935.568140961864847527.davem@davemloft.net> (raw)
In-Reply-To: <1394125601-27685-1-git-send-email-fw@strlen.de>
From: Florian Westphal <fw@strlen.de>
Date: Thu, 6 Mar 2014 18:06:41 +0100
> Quoting Alexander Aring:
> While fragmentation and unloading of 6lowpan module I got this kernel Oops
> after few seconds:
>
> BUG: unable to handle kernel paging request at f88bbc30
> [..]
> Modules linked in: ipv6 [last unloaded: 6lowpan]
> Call Trace:
> [<c012af4c>] ? call_timer_fn+0x54/0xb3
> [<c012aef8>] ? process_timeout+0xa/0xa
> [<c012b66b>] run_timer_softirq+0x140/0x15f
>
> Problem is that incomplete frags are still around after unload; when
> their frag expire timer fires, we get crash.
>
> When a netns is removed (also done when unloading module), inet_frag
> calls the evictor with 'force' argument to purge remaining frags.
>
> The evictor loop terminates when accounted memory ('work') drops to 0
> or the lru-list becomes empty. However, the mem accounting is done
> via percpu counters and may not be accurate, i.e. loop may terminate
> prematurely.
>
> Alter evictor to only stop once the lru list is empty when force is
> requested.
>
> Reported-by: Phoebe Buckheister <phoebe.buckheister@itwm.fraunhofer.de>
> Reported-by: Alexander Aring <alex.aring@gmail.com>
> Tested-by: Alexander Aring <alex.aring@gmail.com>
> Signed-off-by: Florian Westphal <fw@strlen.de>
Applied and queued up for -stable, thanks.
prev parent reply other threads:[~2014-03-06 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 17:06 [PATCH net] inet: frag: make sure forced eviction removes all frags Florian Westphal
2014-03-06 17:36 ` Eric Dumazet
2014-03-07 8:56 ` Jesper Dangaard Brouer
2014-03-07 18:09 ` David Miller
2014-03-06 20:29 ` David Miller [this message]
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=20140306.152935.568140961864847527.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).