Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Mike Kazantsev <mk.fraggod@xxxxxxxxx>
Subject: Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
From: Eric Dumazet <eric.dumazet@xxxxxxxxx>
Date: Mon, 22 Oct 2012 17:22:17 +0200
Cc: Paul Moore <paul@xxxxxxxxxxxxxx>, netdev@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx
Delivered-to: linux-mm-outgoing@xxxxxxxxx
Delivered-to: int-list-linux-mm@xxxxxxxxx
Delivered-to: linux-mm@xxxxxxxxx
In-reply-to: <1350918997.8609.858.camel@edumazet-glaptop>

On Mon, 2012-10-22 at 17:16 +0200, Eric Dumazet wrote:

> OK, I believe I found the bug in IPv4 defrag / IPv6 reasm
> 
> Please test the following patch.
> 
> Thanks !

I'll send a more generic patch in a few minutes, changing
kfree_skb_partial() to call skb_release_head_state()





--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>

Follow-Ups:
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Eric Dumazet

References:
- PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Mike Kazantsev
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Mike Kazantsev
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Paul Moore
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Mike Kazantsev
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Mike Kazantsev
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Mike Kazantsev
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Eric Dumazet
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Mike Kazantsev
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Mike Kazantsev
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Mike Kazantsev
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Eric Dumazet
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Mike Kazantsev
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Eric Dumazet
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Mike Kazantsev
- Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
  - From: Eric Dumazet

Prev by Date: Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
Next by Date: Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
Previous by thread: Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
Next by thread: Re: PROBLEM: Memory leak (at least with SLUB) from "secpath_dup" (xfrm) in 3.5+ kernels
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]