selftests/binderfs: Improve message to provide more info

Currently the binderfs test says what failure it encountered
without saying why it may occurred when it fails to mount
binderfs. So, Warn about enabling CONFIG_ANDROID_BINDERFS in the
running kernel.

Signed-off-by: Karthik Alapati <mail@karthek.com>
Reviewed-by: Christian Brauner (Microsoft) <brauner@kernel.org>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>

diff --git a/tools/testing/selftests/filesystems/binderfs/binderfs_test.c b/tools/testing/selftests/filesystems/binderfs/binderfs_test.c
index 0315955ff0f41df9f0a9b168582a84f914a694aa..bc1c407651fc27cbb751ff3ba8063ff12d93fb76 100644 (file)
--- a/tools/testing/selftests/filesystems/binderfs/binderfs_test.c
+++ b/tools/testing/selftests/filesystems/binderfs/binderfs_test.c
@@ -412,7 +412,8 @@ TEST(binderfs_stress)
 
                ret = mount(NULL, binderfs_mntpt, "binder", 0, 0);
                ASSERT_EQ(ret, 0) {
-                       TH_LOG("%s - Failed to mount binderfs", strerror(errno));
+                       TH_LOG("%s - Failed to mount binderfs, check if CONFIG_ANDROID_BINDERFS is enabled in the running kernel",
+                               strerror(errno));
                }
 
                for (int i = 0; i < ARRAY_SIZE(fds); i++) {