From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Bart De Schuymer <bdschuym@pandora.be>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: Alignment problem with ebt_among
Date: Wed, 10 Sep 2008 16:43:54 +0200 [thread overview]
Message-ID: <48C7DD2A.8000004@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0809101027500.24942@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Wednesday 2008-09-10 10:23, Patrick McHardy wrote:
>>> but this of course breaks the binary interface between userspace and
>>> kernel. Possible solutions I can think of:
>>>
>>> (a) kill ebt_among
>>> (b) willingly change it and break ABI
>>> (c) continue planned transformation to Xtables and fix later
>>>
>>> Which should it be?
>> How about:
>>
>> (d) add compat support to ebtables, transform to xtables,
>> add compat translation
>
> That's the same as (c) for me ;-)
> except that the order is slightly different -- I think the patches
> would also be smaller if we went for Xtables first, because its
> structs at least already have the compat members, for example.
Thats true, its easier to do it the other way around since
you don't have to add compat support to ebtables while its
still standalone, just to delete it in following patches
again.
OTOH, 99% of the core compat support is contained in the
*_tables files anyway, so the difference should be very small.
If you take the route I asked you to, namely first making
ebtables and xtables structs and return conventions match
before doing the actual conversion to use the x_tables
infrastructure, you could already use the compat helpers.
This should result in a fully bisectable set of changes.
next prev parent reply other threads:[~2008-09-10 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 14:07 Alignment problem with ebt_among Jan Engelhardt
2008-09-10 14:23 ` Patrick McHardy
2008-09-10 14:29 ` Jan Engelhardt
2008-09-10 14:43 ` Patrick McHardy [this message]
2008-10-06 0:57 ` 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=48C7DD2A.8000004@trash.net \
--to=kaber@trash.net \
--cc=bdschuym@pandora.be \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.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