From 853dd84c14fc7088d97d5cf35a5185fcecc3b9ae Mon Sep 17 00:00:00 2001 From: Aleksandr Nogikh Date: Wed, 29 Jan 2025 13:39:11 +0100 Subject: dashboard/config/linux: temporarily disable BINDERFS It's currently broken even in torvalds, so if we don't disable it for some time we risk not updating all kernel images for several more weeks. --- dashboard/config/linux/bits/subsystems.yml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'dashboard/config/linux/bits') diff --git a/dashboard/config/linux/bits/subsystems.yml b/dashboard/config/linux/bits/subsystems.yml index 26d12f56a..3344f78a5 100644 --- a/dashboard/config/linux/bits/subsystems.yml +++ b/dashboard/config/linux/bits/subsystems.yml @@ -475,7 +475,9 @@ 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" - - ANDROID_BINDERFS + # TODO: re-enable it once https://syzkaller.appspot.com/bug?id=7dd1c14ce6722e56847192a2741b27a56cc42f5c + # is addressed. + - ANDROID_BINDERFS: [-v6.13, -linux-next] - COUNTER - VALIDATE_FS_PARSER - PSTORE -- cgit mrf-deployment