netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 5/7] netfilter: ebtables: add CONFIG_COMPAT support
Date: Fri, 5 Feb 2010 14:52:26 +0100	[thread overview]
Message-ID: <20100205135226.GA21611@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <1265334195-28120-6-git-send-email-fw@strlen.de>

Florian Westphal <fw@strlen.de> wrote:
> remaining problem:
> 
> The ebtables userland makefile has:
> ifeq ($(shell uname -m),sparc64)
> 	CFLAGS+=-DEBT_MIN_ALIGN=8 -DKERNEL_64_USERSPACE_32
> endif
> 
> struct ebt_replace, ebt_entry_match etc. then contain userland-side
> padding -- this means, if this is actually used in production --
> that even if we are called from a 32 bit userland, the structures
> may already be in the right format.
> 
> One possible solution would be to try to handle compat_* calls via
> the native handler and then fall back to the compat one if it fails,
> but it will cause kernel warnings like:
> kernel msg: ebtables bug: please report to author: Wrong size
> 
> Thus this is not done here.
> 
> I am not sure if this "userland-padding" is widely used; it looks
> incomplete (eg. I couldn't find any
> userland-padding for match/target structures; and some (eg. mark)
> do need special handling).

Just for the record:

Jan Engelhardt was so kind to try "-j mark" with the 32bit
sparc ebtables userland and reported that it is not working.

So I am not sure if I should bother with supporting the "already padded"
userland scenario, as it won't work in some cases anyway.

  reply	other threads:[~2010-02-05 13:52 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 [this message]
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
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=20100205135226.GA21611@Chamillionaire.breakpoint.cc \
    --to=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).