On Sun, Jan 26, 2020 at 09:55:35AM +0100, Greg Kroah-Hartman wrote: > On Sat, Jan 25, 2020 at 06:49:49PM +0100, Dmitry Vyukov wrote: > > Hi binder maintainers, > > > > It seems that something has happened and now syzbot has 0 coverage in > > drivers/android/binder.c: > > https://storage.googleapis.com/syzkaller/cover/ci-upstream-kasan-gce-root.html > > It covered at least something there before as it found some bugs in binder code. > > I _suspect_ it may be related to introduction binderfs, but it's > > purely based on the fact that binderfs changed lots of things there. > > And I see it claims to be backward compatible. > > It is backwards compatible if you mount binderfs, right? Yes, it is backwards compatible. The devices that would usually be created in devtmpfs are now created in binderfs. The core binder-codepaths are the same. Christian _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
