On Sat Aug 16, 2025 at 7:32 PM CEST, Greg Kroah-Hartman wrote:
> On Sat, Aug 16, 2025 at 07:26:16PM +0200, Diederik de Haas wrote:
>> On Sat Aug 16, 2025 at 6:37 PM CEST, Todd Kjos wrote:
>> > This is not feasible since binder relies on many kernel internal functions
>> > and data that cannot be exported for loadable module. Patches for this have
>> > been attempted in the past, but soundly rejected. You can see some of that
>> > discussion at
>> > https://lore.kernel.org/lkml/20180730143710.14413-1-christian@brauner.io/.
>> 
>> That seems to be the upstreaming attempt (or at least trying to start a
>> discussion about it) of the initial patch.
>> A lot could've happened in these 7 years, but apparently not enough for
>> a different outcome. Good to know, thanks :-)
>> 
>> FWIW these are the current ones:
>> https://salsa.debian.org/kernel-team/linux/-/blob/debian/6.16.1-1_exp1/debian/patches/debian/export-symbols-needed-by-binder.patch
>
> Ah, that makes more sense, that patch is not going to be accepted
> upsteam sorry.

I deliberately didn't link to those patches in my OP as I wanted to know
if it was possible/feasible at all (perhaps with some rework). I was
pretty sure if I had, the discussion would've only been about that
specific implementation.

The functionality (ie having the possibility to run Waydroid) seems
appealing (even ideal) to me, but (for myself) I didn't want to make it
built-in and having it available as a loadable module seems like a
great way to have both options in my (and other's) kernel.
And a functionality which should be available upstream if at all.

Cheers,
  Diederik