[PATCH] Check net->nfnl for NULL in ctnetlink_conntrack_event to, avoid Oops on container destroy · Tim Gardner <hidden> · 2011-09-12
Re: [PATCH] Check net->nfnl for NULL in ctnetlink_conntrack_event to, avoid Oops on container destroy · Tim Gardner <hidden> · 2011-09-12
Re: [PATCH] Check net->nfnl for NULL in ctnetlink_conntrack_event to, avoid Oops on container destroy · Julian Anastasov <ja@ssi.bg> · 2011-09-12
Re: [PATCH] Check net->nfnl for NULL in ctnetlink_conntrack_event to, avoid Oops on container destroy · Pablo Neira Ayuso <pablo@netfilter.org> · 2011-09-14

Re: [PATCH] Check net->nfnl for NULL in ctnetlink_conntrack_event to, avoid Oops on container destroy

From: Pablo Neira Ayuso <pablo@netfilter.org>
Date: 2011-09-14 12:31:44
Also in: lkml, netfilter-devel

On Mon, Sep 12, 2011 at 12:03:13PM -0600, Tim Gardner wrote:

Patrick,

I received this patch from a developer that uses lxc and network
name spaces. I don't know the locking semantics well enough for CT
to judge whether this fix is sufficient. Bug info can be found at
http://bugs.launchpad.net/bugs/843892 . See comment #7 for his
analysis.

We're still discussing a better solution for it.

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help