diff options
| author | Karthik Alapati <[email protected]> | 2022-04-23 11:14:34 +0530 |
|---|---|---|
| committer | Shuah Khan <[email protected]> | 2022-04-25 10:04:42 -0600 |
| commit | ea1d15a067d601cf156c042bd0834acad67db650 (patch) | |
| tree | 63e2e6f8c70f2453e32a0bcd032f8fdb3929f50d /tools/testing/selftests/filesystems/binderfs/binderfs_test.c | |
| parent | abd26d348b2a366f8947e8c3c2ab9bc881ac9415 (diff) | |
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 <[email protected]>
Reviewed-by: Christian Brauner (Microsoft) <[email protected]>
Signed-off-by: Shuah Khan <[email protected]>
Diffstat (limited to 'tools/testing/selftests/filesystems/binderfs/binderfs_test.c')
| -rw-r--r-- | tools/testing/selftests/filesystems/binderfs/binderfs_test.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/tools/testing/selftests/filesystems/binderfs/binderfs_test.c b/tools/testing/selftests/filesystems/binderfs/binderfs_test.c index 0315955ff0f4..bc1c407651fc 100644 --- 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++) { |