linux-kernel - Re: [PATCH] Fix repeatable Oops on container destroy with conntrack

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <A51A04647674405AF6C39A4F@nimrod.local>
Date:	Wed, 14 Sep 2011 09:01:34 +0100
From:	Alex Bligh <alex@...x.org.uk>
To:	Pablo Neira Ayuso <pablo@...filter.org>
cc:	Alexey Dobriyan <adobriyan@...il.com>,
	netfilter-devel@...r.kernel.org, netfilter@...r.kernel.org,
	coreteam@...filter.org, linux-kernel@...r.kernel.org,
	containers@...ts.linux-foundation.org,
	Linux Containers <containers@...ts.osdl.org>,
	Alex Bligh <alex@...x.org.uk>
Subject: Re: [PATCH] Fix repeatable Oops on container destroy with conntrack

--On 14 September 2011 03:35:00 +0200 Pablo Neira Ayuso 
<pablo@...filter.org> wrote:

>> Is this new version OK? I am happy to adjust if not.
>
> Hm, I still think that this is a workaround.

It is a bit of a workaround, that is true. But it is a workaround
that will fix the bug in every kernel since 2.6.32 (and perhaps
before - I haven't looked). It's thus reasonably easily applicable
to stable kernel series.

I'm not clued-up enough on Netfilter to know what the right fix is,
but is applying the workaround in a commit which could be easily
backported, then applying the 'right fix' (assuming that is different)
a reasonable strategy?

As you can probably tell, my interest here is to get something that
doesn't oops into stable kernels.

-- 
Alex Bligh
--
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/