From 44dc9245e7fa98cab395019094dd18506f4cf1db Mon Sep 17 00:00:00 2001 From: Alan Somers Date: Thu, 21 Mar 2019 21:41:07 +0000 Subject: [PATCH] fusefs: don't check for the fusefs module during the tests It's sufficient to check for /dev/fuse. And due to bug 236647, the module could be named either fuse or fusefs. PR: 236647 Sponsored by: The FreeBSD Foundation --- tests/sys/fs/fusefs/utils.cc | 5 ----- 1 file changed, 5 deletions(-) diff --git a/tests/sys/fs/fusefs/utils.cc b/tests/sys/fs/fusefs/utils.cc index 3ca9bd7d6e0..f68d46ffbe5 100644 --- a/tests/sys/fs/fusefs/utils.cc +++ b/tests/sys/fs/fusefs/utils.cc @@ -43,15 +43,10 @@ using namespace testing; /* Check that fusefs(4) is accessible and the current user can mount(2) */ void check_environment() { - const char *mod_name = "fusefs"; const char *devnode = "/dev/fuse"; const char *usermount_node = "vfs.usermount"; int usermount_val = 0; size_t usermount_size = sizeof(usermount_val); - if (modfind(mod_name) == -1) { - GTEST_SKIP() << "Module " << mod_name << - " could not be resolved"; - } if (eaccess(devnode, R_OK | W_OK)) { if (errno == ENOENT) { GTEST_SKIP() << devnode << " does not exist";