d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

fusefs: don't check for the fusefs module during the tests

Browse Source 
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
This commit is contained in:
Alan Somers 2019-03-21 21:41:07 +00:00
parent 91ff3a0d3d
commit 44dc9245e7
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/projects/fuse2/; revision=345386
1 changed files with 0 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
tests/sys/fs/fusefs/utils.cc
View File

@ -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";