From: David Miller <davem@davemloft.net>
To: fw@strlen.de
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] xfrm: x86_64 CONFIG_COMPAT support
Date: Fri, 05 Feb 2010 11:59:13 -0800 (PST) [thread overview]
Message-ID: <20100205.115913.103119415.davem@davemloft.net> (raw)
In-Reply-To: <20100205195409.GB23792@Chamillionaire.breakpoint.cc>
From: Florian Westphal <fw@strlen.de>
Date: Fri, 5 Feb 2010 20:54:09 +0100
> I had a look at the wireless compat layer you mentioned;
> when sending data to userspace one just prepares two
> skbs (one native, one compat); netlink_recvmsg() then decides
> which one to use for a particular receiver.
>
> However, I believe I can use is_compat_task() on
> the userspace -> kernel side to figure out how to interpret
> the incoming data.
>
> Is that correct or did I misunderstand?
Again, you can't use is_compat_task().
Just like netlink_recvmsg() you should use MSG_CMSG_COMPAT.
If it isn't be set correctly, you need to find out why.
next prev parent reply other threads:[~2010-02-05 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 1:47 [RFC] xfrm: x86_64 CONFIG_COMPAT support Florian Westphal
2010-02-05 4:22 ` David Miller
2010-02-05 19:54 ` Florian Westphal
2010-02-05 19:59 ` David Miller [this message]
2010-02-05 21:13 ` Florian Westphal
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=20100205.115913.103119415.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fw@strlen.de \
--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;
as well as URLs for NNTP newsgroup(s).