linux-kernel - Re: Fwd: [RFC][PATCH] staging: Fix build issues with new binder API

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] [day] [month] [year] [list]

Message-ID: <530F9001.8040608@linaro.org>
Date:	Thu, 27 Feb 2014 11:20:33 -0800
From:	John Stultz <john.stultz@...aro.org>
To:	Arnd Bergmann <arnd.bergmann@...aro.org>
CC:	Greg KH <gregkh@...uxfoundation.org>,
	Colin Cross <ccross@...roid.com>,
	Arve Hjønnevåg <arve@...roid.com>,
	Serban Constantinescu <serban.constantinescu@....com>,
	Android Kernel Team <kernel-team@...roid.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Fwd: [RFC][PATCH] staging: Fix build issues with new binder API

On 02/27/2014 11:15 AM, Arnd Bergmann wrote:
> On Wednesday 26 February 2014, John Stultz wrote:
>> The new 64bit binder API causes build issues on 32bit ARM
>> due to the lack of 64bit __get_user_asm_* implementation.
> It is impossible to implement this. Many have tried before.
>
>> Until that implementation is done, remove the choice for
>> 32bit ARM, automatically enabling the old 32bit binder
>> protocol.
>>
>> This can be reverted once a 64bit __get_user_asm_*
>> implementation is merged.
> I think the best solution is to use __copy_from_user for
> the 64-bit access. You can wrap it in a helper function
> if you want to speed up the native-word-size case.

Ah. Thanks for the context and the tip. Will try to get an appropriate
solution there then.

thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/