Re: [PATCH v3 1/2] binder: Add default binder devices through binderfs when configured
From: Greg Kroah-Hartman
Date: Fri Aug 09 2019 - 10:50:20 EST
On Thu, Aug 08, 2019 at 03:27:25PM -0700, Hridya Valsaraju wrote:
> Currently, since each binderfs instance needs its own
> private binder devices, every time a binderfs instance is
> mounted, all the default binder devices need to be created
> via the BINDER_CTL_ADD IOCTL.
Wasn't that a design goal of binderfs?
> This patch aims to
> add a solution to automatically create the default binder
> devices for each binderfs instance that gets mounted.
> To achieve this goal, when CONFIG_ANDROID_BINDERFS is set,
> the default binder devices specified by CONFIG_ANDROID_BINDER_DEVICES
> are created in each binderfs instance instead of global devices
> being created by the binder driver.
This is going to change how things work today, what is going to break
because of this change?
I don't object to this, except for the worry of changing the default
behavior.
thanks,
greg k-h