All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6668] New: iptables limit module alignment problem on mips64
Date: Tue,  5 Nov 2013 16:32:08 +0000 (UTC)	[thread overview]
Message-ID: <bug-6668-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=6668

           Summary: iptables limit module alignment problem on mips64
           Product: buildroot
           Version: unspecified
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: cassiano at idbinfo.com.br
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


iptables limit module causes an alignment error on a 64-bit kernel and 32-bit
userland. After inserting a rule containing limit, any other operation results
in the following message on kernel dmesg:

x_tables: ip_tables: limit.0 match: invalid size 40 (kernel) != (user) 48

looking at the limit code, its the only one module that uses CONFIG_COMPAT for
legacy code.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2013-11-05 16:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 16:32 bugzilla at busybox.net [this message]
2013-11-09 21:55 ` [Buildroot] [Bug 6668] iptables limit module alignment problem on mips64 bugzilla at busybox.net
2013-11-10 21:18 ` bugzilla at busybox.net
2013-11-11 12:12 ` bugzilla at busybox.net
2013-11-11 16:23 ` bugzilla at busybox.net

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=bug-6668-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.