From: Patrick McHardy <kaber@trash.net>
To: Florian Westphal <fw@strlen.de>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH v3 0/4] xfrm: add x86 CONFIG_COMPAT support
Date: Wed, 07 Apr 2010 15:45:51 +0200 [thread overview]
Message-ID: <4BBC8C8F.9020907@trash.net> (raw)
In-Reply-To: <20100407133528.GD22518@Chamillionaire.breakpoint.cc>
Florian Westphal wrote:
> David Miller <davem@davemloft.net> wrote:
>> From: Florian Westphal <fw@strlen.de>
>> Date: Tue, 6 Apr 2010 00:27:07 +0200
>
> [..]
>
>>> I sent a patch that solved this by adding a sys_compat_write syscall
>>> and a ->compat_aio_write() to struct file_operations to the
>>> vfs mailing list, but that patch was ignored by the vfs people,
>>> and the x86 folks did not exactly like the idea either.
>>>
>>> So this leaves three alternatives:
>>> 1 - drop the whole idea and keep the current status.
>>> 2 - Add new structure definitions (with new numbering) that would work
>>> everywhere, keep the old ones for backwards compatibility (This
>>> was suggested by Arnd Bergmann).
Given that there is only a quite small number of users of this
interface, that would in my opinion be the best way.
>>> 3 - apply this patch set and tell userspace to move the sendmsg() when
>>> they want to work with xfrm on x86_64 with 32 bit userland.
>> So do we know of any xfrm netlink apps that do not use sendmsg()?
next prev parent reply other threads:[~2010-04-07 13:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 22:27 [PATCH v3 0/4] xfrm: add x86 CONFIG_COMPAT support Florian Westphal
2010-04-05 22:27 ` [PATCH 1/4] netlink: append NLMSG_DONE to compatskb, too Florian Westphal
2010-04-05 22:27 ` [PATCH 2/4] netlink: store MSG_CMSG_COMPAT flag in netlink_skb_parms Florian Westphal
2010-04-05 22:27 ` [PATCH 3/4] xfrm: split nlmsg allocation and data copying Florian Westphal
2010-04-05 22:27 ` [PATCH 4/4] xfrm: CONFIG_COMPAT support for x86 architecture Florian Westphal
2010-04-07 10:08 ` [PATCH v3 0/4] xfrm: add x86 CONFIG_COMPAT support David Miller
2010-04-07 13:35 ` Florian Westphal
2010-04-07 13:45 ` Patrick McHardy [this message]
2010-04-07 23:48 ` David Miller
2010-04-08 9:44 ` Patrick McHardy
2010-04-08 9:54 ` David Miller
2010-04-08 11:24 ` Patrick McHardy
2010-04-08 5:00 ` David Miller
2010-05-13 6:41 ` David Miller
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=4BBC8C8F.9020907@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=johannes@sipsolutions.net \
--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 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.