lkml.org 
[lkml]   [2017]   [Sep]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] android: binder: fix type mismatch warning
On Mon, Sep 18, 2017 at 05:35:03PM +0200, Arnd Bergmann wrote:
> On Mon, Sep 18, 2017 at 4:02 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >> However, there is another problem with the Kconfig option: turning
> >> it on or off creates two incompatible ABI versions, a kernel that
> >> has this enabled cannot run user space that was built without it
> >> or vice versa. A better solution might be to leave the option hidden
> >> until the binder code is fixed to deal with both ABI versions.
> >
> > I don't know if that is ever going to be fixed, as it's not an issue
> > that you will ever see "in the wild" from what I can tell...
>
> Probably not on a native Android device or even a Chromebook that
> ships a binder user space together with a kernel, but what about
> people using "anbox" or similar projects that allow you to run
> Android apps in a container?

Ugh, that's crazy, binder should not be run that way due to a variety of
issues... Well, as of 4.14 those issues will be gone, so no one is
doing this yet :)

> It seems like a legitimate use case of the binder modules, but
> now there is a kernel Kconfig option that has to match a user
> space binary.

So, should we revert that?

I don't really know what to suggest here, sorry...

greg k-h

\
 
 \ /
  Last update: 2017-09-18 17:54    [W:0.099 / U:2.760 seconds]
©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site