All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Sharat Masetty <sharat04@gmail.com>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: Re: ebtables issue in compat mode
Date: Sat, 3 May 2014 00:31:39 +0200	[thread overview]
Message-ID: <20140502223139.GA3514@breakpoint.cc> (raw)
In-Reply-To: <CAJzFV37Vus34O9F+0ATW6s6-5=OgTBLAxJ1rC6_658x25dNWzw@mail.gmail.com>

Sharat Masetty <sharat04@gmail.com> 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.

  parent reply	other threads:[~2014-05-02 22:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-01  5:18 ebtables issue in compat mode Sharat Masetty
2014-05-01 10:02 ` Florian Westphal
2014-05-01 16:09   ` Sharat Masetty
2014-05-01 21:50     ` Sharat Masetty
2014-05-02 22:31     ` Florian Westphal [this message]
2014-05-02 22:35       ` Jan Engelhardt
2014-05-02 22:37         ` Florian Westphal
2014-05-03  1:06           ` Sharat Masetty
2014-05-04 21:05             ` Bart De Schuymer
2014-05-03  1:23           ` Jan Engelhardt
2014-05-04 21:04     ` Bart De Schuymer
  -- strict thread matches above, loose matches on Subject: below --
2014-05-02 19:05 Sharat Masetty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140502223139.GA3514@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=sharat04@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.