[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1300730838.2884.578.camel@edumazet-laptop>
Date: Mon, 21 Mar 2011 19:07:18 +0100
From: Eric Dumazet <eric.dumazet@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: David Miller <davem@...emloft.net>, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>,
Arnd Bergmann <arnd@...db.de>,
Pekka Enberg <penberg@...helsinki.fi>,
Simon Horman <horms@...ge.net.au>
Subject: Re: [slab poison overwritten] Re: [GIT] Networking
Le lundi 21 mars 2011 à 18:39 +0100, Ingo Molnar a écrit :
> here's the same but with kallsyms enabled.
>
> Thanks,
>
> Ingo
>
> [ 9.585627] initcall 0xffffffff81d5b806 returned 0 after 0 usecs
> [ 9.588960] calling 0xffffffff81d5b9da @ 1
> [ 9.592303] IPVS: Creating netns size=1272 id=0
> [ 9.595646] IPVS: __ip_vs_control_init(): alloc_percpu.
> [ 9.602298] IPVS: cannot register namespace.
> [ 9.605627] IPVS: can't setup control
It seems IPVS is busted in case of memory allocation error in
__ip_vs_control_init()
IPVS deinits its "struct netns_ipvs" space, but something (in IPVS) uses
it after free.
__ip_vs_init() seems to be called before ip_vs_init() completes
correctly. We then keep in net->ipvs a pointer to some freed memory.
Commit 14e405461e664b7 did some changes in this area
Simon, any idea ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists