From mboxrd@z Thu Jan 1 00:00:00 1970 From: Florian Westphal Subject: Re: ebtables issue in compat mode Date: Sat, 3 May 2014 00:31:39 +0200 Message-ID: <20140502223139.GA3514@breakpoint.cc> References: <20140501100229.GS31953@breakpoint.cc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Florian Westphal , netfilter-devel@vger.kernel.org To: Sharat Masetty Return-path: Received: from Chamillionaire.breakpoint.cc ([80.244.247.6]:58974 "EHLO Chamillionaire.breakpoint.cc" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752806AbaEBWbl (ORCPT ); Fri, 2 May 2014 18:31:41 -0400 Content-Disposition: inline In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: Sharat Masetty wrote: > We are using a 3.10.0 kernel version which has CONFIG_COMPAT enabled. > The ebtables version is 2.0.10-4. This is arm 63/32 not x86. FWIW i have no issues with 2.0.10-4 either (on x86), so its hard for me to debug this since I don't have access to a aarch64/arm64 machine. > Please let me know what to watch out for My guess would be that ebt_size_mwt() in size_entry_mwt() fails to account for some required padding. You could #define DEBUG at the top of it and see the offset fixup that it tries to make. Should be fairly simple to build a ebtables64 binary and check what the expected values should be.