netdev - Re: [RFC] xfrm: x86_64 CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100205.115913.103119415.davem@davemloft.net>
Date:	Fri, 05 Feb 2010 11:59:13 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	fw@...len.de
Cc:	netdev@...r.kernel.org
Subject: Re: [RFC] xfrm: x86_64 CONFIG_COMPAT support

From: Florian Westphal <fw@...len.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html