All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart De Schuymer <bdschuym@pandora.be>
To: Sharat Masetty <sharat04@gmail.com>, Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: ebtables issue in compat mode
Date: Sun, 04 May 2014 23:04:32 +0200	[thread overview]
Message-ID: <5366AB60.7020009@pandora.be> (raw)
In-Reply-To: <CAJzFV37Vus34O9F+0ATW6s6-5=OgTBLAxJ1rC6_658x25dNWzw@mail.gmail.com>

Sharat Masetty schreef op 1/05/2014 18:09:
> 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.
> I also have another question. Do we need to compile the userspace tool
> using the sanitized kernel headers?(uapi/linux) or should we be using
> headers provided in the ebtables user space package? The reason for
> asking this question is that I see some differences in the structure
> definitions between the ebtables packaged kernel header files and the
> header files exposed by the kernel.

The kernel should be backwards compatible, so using the provided header 
files should be fine.

cheers,
Bart


  parent reply	other threads:[~2014-05-04 21:04 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
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 [this message]
  -- 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=5366AB60.7020009@pandora.be \
    --to=bdschuym@pandora.be \
    --cc=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.