From: Amin Azez Subject: Re: [PATCH] priv_data 0/2 Date: Fri, 21 Jul 2006 10:52:15 +0100 Message-ID: <44C0A3CF.9020702@ufomechanic.net> References: <200606261641.47294.max@nucleus.it> <44A962DF.3080406@trash.net> <200607032305.06581.max@nucleus.it> <44A9A103.8090705@anduras.de> <44A9B458.1030106@trash.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: netfilter-devel@lists.netfilter.org Return-path: To: Patrick McHardy In-Reply-To: <44A9B458.1030106@trash.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-devel-bounces@lists.netfilter.org Errors-To: netfilter-devel-bounces@lists.netfilter.org List-Id: netfilter-devel.vger.kernel.org * Patrick McHardy wrote, On 04/07/06 01:20: > Sven Anders wrote: >> If this is merged, I would like to see a negated limit... >> I need some advice to preserve compatibility here. > > Once this is merged we can convert matches and targets to keep their > private state outside of the structure shared with userspace and can > start reusing the fields, since they are ignored by userspace anyway. > I'm not sure, but I think currently userspace initializes them to 0, > which should make this easy. Relying on userspace to initialize kernel structures to 0 smells like danger, and a possible exploit point. Sam