Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#64778 - [linux] Enable android/binder

Attached to Project: Arch Linux
Opened by LucaS (luca020400) - Sunday, 08 December 2019, 21:14 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 01 March 2022, 21:31 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 8
Private No


Would it be possible to enable the android config and then binder related configs?


as seen here
A few more info regarding binderfs

Additional info:
* package version(s): linux-5.4.2
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 01 March 2022, 21:31 GMT
Reason for closing:  Fixed
Comment by Jensen McKenzie (your_doomsday) - Monday, 09 December 2019, 11:58 GMT
What would be the use case? Arch support only x86_64 Platform. I don't think any major linux distro enables this.
Comment by LucaS (luca020400) - Monday, 09 December 2019, 12:02 GMT
The usecase would be mainly testing IPC.
This is one of the most used mechanism used on mobile phones and would make testing easier.
The impact is really small
And I agree that probably no one enables this
Comment by Jan Alexander Steffens (heftig) - Friday, 21 February 2020, 21:34 GMT
It can't be built as a module. I would rather keep it disabled.
Comment by LucaS (luca020400) - Friday, 21 February 2020, 21:37 GMT
I haven't thought about that, I'm used to more bare-metal development where everything is built-in.
I'll see if I can get it building as a module and upstream it.
Comment by Daniel Parks (danielrparks) - Saturday, 08 August 2020, 01:24 GMT Comment by Adam (adam900710) - Monday, 28 September 2020, 12:03 GMT
Another use case for arch kernel with android binder and other mechanism is to make default arch kernel compatible with anbox.

So personally speaking I'm pretty happy to enable that if we can't compile them as module for kernel >= 5.7.0.
Comment by Daniel Parks (danielrparks) - Monday, 28 September 2020, 15:07 GMT
I think that the impact of enabling them would be fairly low, as would the security risk, since it gets enough usage through Android that it would fall under proper scrutiny. I can see why heftig wouldn't want to enable it, though (or patch the kernel to enable building as modules). Unless anbox suddenly becomes very popular, it would be a waste of resources to the majority of users.

Maybe the best course of action would be to ask Zen kernel to upstream the Debian patches. It's already an "alternative" kernel, so this might be the path with the least friction.
Comment by Jan Alexander Steffens (heftig) - Friday, 02 October 2020, 16:50 GMT
Implemented in linux-zen 5.8.13.zen1-2 for /  FS#68077 
Comment by Adam (adam900710) - Saturday, 24 October 2020, 11:54 GMT
Not to offend zen guys, but personally speaking some features are questionable like hard kernel preemption, which puts the user beyond bleeding edge.
While the Android code is already mainlined, tested by android already.

On the other hand, tons of arch kernel features are already a waste of space for most users.
Are you saying things like CONFIG_NF_CT_PROTO_SCTP/DCCP would really benefit most Arch users?

I understand the packager don't want to add features he or she is not familiar with, but also shouldn't be an excuse not to enable something with potential users.
I'd say Anbox users are definitely more than SCTP/DCCP netfilter connection tracking users, while the the latter functions are already compiled into current Arch kernel.

But still a big thank to the zen kernel support, at least users have a choice without re-compiling the kernel themselves.