From: Florian Westphal <fw@strlen.de>
To: Chris Friesen <chris.friesen@genband.com>
Cc: netdev@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] problems with "ip xfrm" on 32-bit userspace with 64-bit kernel
Date: Thu, 21 Oct 2010 09:50:56 +0200 [thread overview]
Message-ID: <20101021075056.GE15247@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <4CBF78B6.90002@genband.com>
Chris Friesen <chris.friesen@genband.com> wrote:
> We've run into a 32/64 compatibility problem with iproute2. The "ip
> xfrm monitor acquire" command doesn't work properly due to struct size
> mismatches between kernel and userspace.
Yes. See archives for 'xfrm: add x86 CONFIG_COMPAT support'
(http://marc.info/?t=127050655600003&r=1&w=2)
for a discussion on why the patch set to fix this was rejected.
next prev parent reply other threads:[~2010-10-21 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 23:18 [BUG] problems with "ip xfrm" on 32-bit userspace with 64-bit kernel Chris Friesen
2010-10-21 7:50 ` Florian Westphal [this message]
2010-10-21 15:05 ` Chris Friesen
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=20101021075056.GE15247@Chamillionaire.breakpoint.cc \
--to=fw@strlen.de \
--cc=chris.friesen@genband.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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