mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Diederik de Haas" <didi.debian@cknow.org>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: "Todd Kjos" <tkjos@google.com>,
	"Arve Hjønnevåg" <arve@android.com>,
	"Todd Kjos" <tkjos@android.com>,
	"Martijn Coenen" <maco@android.com>,
	"Joel Fernandes" <joelagnelf@nvidia.com>,
	"Christian Brauner" <brauner@kernel.org>,
	"Carlos Llamas" <cmllamas@google.com>,
	"Suren Baghdasaryan" <surenb@google.com>,
	linux-kernel@vger.kernel.org
Subject: Re: RFE: Make ANDROID_BINDER_IPC tristate
Date: Sat, 16 Aug 2025 20:04:00 +0200	[thread overview]
Message-ID: <DC41TPTBHO28.134BL9RYKZLK7@cknow.org> (raw)
In-Reply-To: <2025081612-unpledged-agnostic-7fb3@gregkh>

[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-08-16 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16 12:11 Diederik de Haas
2025-08-16 12:47 ` Greg Kroah-Hartman
2025-08-16 12:52   ` Diederik de Haas
     [not found]     ` <CAHRSSEyxcqydwbEHHLzHKar9AaQAjACFuM0CnBxN5XrvFQdBcw@mail.gmail.com>
2025-08-16 17:26       ` Diederik de Haas
2025-08-16 17:32         ` Greg Kroah-Hartman
2025-08-16 18:04           ` Diederik de Haas [this message]
2025-08-16 17:31       ` Greg Kroah-Hartman

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=DC41TPTBHO28.134BL9RYKZLK7@cknow.org \
    --to=didi.debian@cknow.org \
    --cc=arve@android.com \
    --cc=brauner@kernel.org \
    --cc=cmllamas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joelagnelf@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maco@android.com \
    --cc=surenb@google.com \
    --cc=tkjos@android.com \
    --cc=tkjos@google.com \
    /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

all inboxes | Powered by JetHome®