netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart De Schuymer <bdschuym@pandora.be>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/7] netfilter: ebtables: CONFIG_COMPAT support
Date: Fri, 05 Feb 2010 18:15:29 +0100	[thread overview]
Message-ID: <4B6C5231.7040702@pandora.be> (raw)
In-Reply-To: <20100205140021.GB21611@Chamillionaire.breakpoint.cc>

Hello Florian,

First of all, thanks for pointing out these problems.

Florian Westphal schreef:
> Jan Engelhardt <jengelh@medozas.de> wrote:
>   
>> In a quick look, ebtables 2.0.8-2 seems to just work there in both
>> 32/64 and 64/64 [U/K-bitness] combinations:
>>     
> [..]
>   
>> So I wonder whether extra patches are really needed for x86_64.
>>     
>
> I did investigate the "lets pad the structures in userspace" scenario.
> It has two problems.
>
> First of all, support for a few targets/matches is missing.
>
>   
I would certainly accept patches to the userland code to fix these
remaining problems that I was unaware of. I don't have access to such a
machine.

> Second, the point is to run unmodified binaries with either a 32
> or 64 bit kernel without recompiling.
>
> Solving this transparently (i.e. same binary) would thus
> require a run-time check for the kernel architecture before the
> set/getsockopt can be made.
>
> As far as I could see this would require a lot of changes to the ebtables
> userland code base, too.
>   
Could you elaborate why having to distribute two compiled versions of
ebtables for different platform configurations is more overhead than the
overhead added by your kernel patches? Can't you decide on installation
time of the Linux system which binary to provide?
At this time I am more in favor of fixing userland...

cheers,
Bart

-- 
Bart De Schuymer
www.artinalgorithms.be


  reply	other threads:[~2010-02-05 17:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05  1:43 [PATCH 0/7] netfilter: ebtables: CONFIG_COMPAT support Florian Westphal
2010-02-05  1:43 ` [PATCH 1/7] netfilter: ebtables: abort if next_offset is too small Florian Westphal
2010-02-05  1:43 ` [PATCH 2/7] netfilter: ebtables: avoid explicit XT_ALIGN() in match/targets Florian Westphal
2010-02-05  1:43 ` [PATCH 3/7] netfilter: CONFIG_COMPAT: allow delta to exceed 32767 Florian Westphal
2010-02-05  1:43 ` [PATCH 4/7] netfilter: ebtables: split do_replace into two functions Florian Westphal
2010-02-05  1:43 ` [PATCH 5/7] netfilter: ebtables: add CONFIG_COMPAT support Florian Westphal
2010-02-05 13:52   ` Florian Westphal
2010-02-07 22:43   ` Florian Westphal
2010-02-05  1:43 ` [PATCH 6/7] netfilter: ebt_limit: " Florian Westphal
2010-02-05  1:43 ` [PATCH 7/7] netfilter: ebtables: mark: " Florian Westphal
2010-02-05  7:15 ` [PATCH 0/7] netfilter: ebtables: " Jan Engelhardt
2010-02-05 14:00   ` Florian Westphal
2010-02-05 17:15     ` Bart De Schuymer [this message]
2010-02-05 18:02       ` David Miller
2010-02-06 13:08         ` Bart De Schuymer
2010-02-06 13:50           ` Jan Engelhardt
2010-02-07 22:38           ` Florian Westphal
2010-02-07 23:19             ` Bart De Schuymer
2010-02-07 23:28               ` Florian Westphal
2010-02-05 19:53       ` Florian Westphal
2010-02-05 20:07         ` Jan Engelhardt

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=4B6C5231.7040702@pandora.be \
    --to=bdschuym@pandora.be \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).