> Do we really need someone to do more work that has been done on it in > the past as an official "maintainer"? I'll be glad to do it, as I doubt > it will require any time at all. Well every time in the past that Al Viro looked in its direction he broke it so probably. Someone is going to have to clean up or fix the fact it pokes around in the depths of the low level fd I/O code and calls stuff like __fd_install and __alloc_fd directly, or mend it if it breaks. I'm curious what Al Viro thinks of it > > Currently in the android space no one but libbinder should use the > > kernel interface. > > That is correct. If you do that, you deserve all of the pain and > suffering and rooted machines you will get. So what is the Android side model for its security. That probably also should be described so nobody goes off and uses it for something like systemd because "it looked neat". > But all of the changes will be in new code. Be it kdbus, or something > else if that doesn't work out. This existing binder.c file will not be > changing at all. This existing ABI, and codebase, is something that we > have to maintain forever for those millions of devices out there in the > real world today. 95% of those devices are locked down, most of them have non replaceable batteries that will dead and irreplacable (sanely anyway) in 3-5 years. "Forever" in the phone world is mercifully rather short. Alan _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
