From 1a5d9317ecfa21e32cf9c876306c7b5f665999bf Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Wed, 12 Mar 2025 16:26:53 +0100 Subject: dashboard/config/linux: reenable ANDROID_BINDERFS It is now resolved on torvalds and linux-next. Fixes #5828. --- dashboard/config/linux/bits/subsystems.yml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'dashboard/config/linux/bits/subsystems.yml') diff --git a/dashboard/config/linux/bits/subsystems.yml b/dashboard/config/linux/bits/subsystems.yml index c1964fa20..eb4dc0426 100644 --- a/dashboard/config/linux/bits/subsystems.yml +++ b/dashboard/config/linux/bits/subsystems.yml @@ -475,9 +475,7 @@ config: # Earlier we defined here 32 devices and syzkaller allocated one per test process. # When binderfs is used, we don't need that many - 2 is enough. - ANDROID_BINDER_DEVICES: "binder0,binder1" - # TODO: re-enable it once https://syzkaller.appspot.com/bug?id=7dd1c14ce6722e56847192a2741b27a56cc42f5c - # is addressed. - - ANDROID_BINDERFS: [-v6.13, -linux-next] + - ANDROID_BINDERFS - COUNTER - VALIDATE_FS_PARSER - PSTORE -- cgit mrf-deployment