From: Bart De Schuymer <bdschuym@pandora.be>
To: Sharat Masetty <sharat04@gmail.com>, Florian Westphal <fw@strlen.de>
Cc: Jan Engelhardt <jengelh@inai.de>, netfilter-devel@vger.kernel.org
Subject: Re: ebtables issue in compat mode
Date: Sun, 04 May 2014 23:05:44 +0200 [thread overview]
Message-ID: <5366ABA8.1050906@pandora.be> (raw)
In-Reply-To: <CAJzFV35yO+N_1Hxqn742VrQEi=djutgL6Xbs9FugsLKQXzH6Ww@mail.gmail.com>
Sharat Masetty schreef op 3/05/2014 3:06:
> Thanks for the suggestions, I will dig into it and see if I can
> provide relevant logs here.
>
> Do we have to enabled this define in the userspace?
> KERNEL_64_USERSPACE_32, Tried enabling it and it fails at some other
> location in the kernel. So its unclear whether to enable this or
> not...
That option was introduced and has only been tested for Sparc32/64, so
odds are it doesn't work for your setup (note that you need the
ebtables.h version that comes with the ebtables userspace package). But
a hack similar to that will probably make it work for you (it's a matter
of getting the offsets of the struct members right and translating
32-bit pointers into 64-bit pointers). I thought the whole compat layer
would make this stuff irrelevant. Guess not.
cheers,
Bart
next prev parent reply other threads:[~2014-05-04 21:05 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 [this message]
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=5366ABA8.1050906@pandora.be \
--to=bdschuym@pandora.be \
--cc=fw@strlen.de \
--cc=jengelh@inai.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.