| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
There is no reason why so many tests require the file system
to support unlink() and/or rmdir().
|
|
|
|
|
| |
Ensure that we are really creating a new file.
Don't attempt to write, we do that in tst_open_write().
|
|
|
|
|
| |
We are actually testing both opening of an existing file
and writing to it.
|
|
|
|
| |
To check for unlink() support without requiring create()/mknod().
|
|
|
|
|
| |
This allows testing a filesystem that offers mkdir(), but no
rmdir() (and vice versa).
|
|
|
|
|
| |
This makes more sense, since we are specifically checking
unlinking of an open file.
|
|
|
|
|
|
| |
By creating the files in the lower filesystem, we
can test readdir() even for filesystems that don't implement
create() or mkdir().
|
| |
|
| |
|
| |
|
|
|
|
| |
fi may be NULL, so we need to protect against this.
|
|
|
|
|
|
| |
Several options (use_ino, etc) depend on the file system
implementation. Allowing them to be set from the command line makes no
sense.
|
|
|
|
|
|
| |
Instead of using command line options to modify struct fuse_conn_info
before and after calling the init() handler, we now give the file system
explicit control over this.
|
|
|
|
| |
When running tests as non-root, make fusermount setuid root.
|
| |
|
|
|
|
|
|
|
| |
The fix in commit cf4159156b was incomplete. While some false positives
are caused by sleep() in the file system taking longer than expected,
there was also a race condition where the file system would run before
the contents are initialized properly.
|
| |
|
| |
|
|
|
|
| |
When running under Valgrind, we otherwise get sporadic test failures.
|
|
|
|
|
| |
This should make it more obvious at first glance what the different
examples do.
|
|
|
|
|
| |
The new names should make it more obvious at first glance
what each example demonstrates.
|
|
|
|
| |
Also, added more comments for the same purpose.
|
|
|
|
| |
Fixes #32.
|
|
|
|
|
| |
These examplesdemonstrate the use of the `fuse_lowlevel_notify_store`
and `fuse_lowlevel_notify_inval_inode` functions.
|
|
|
|
|
|
| |
This option is obsolete and should always be enabled. File systems that
want to limit the size of write requests should use the
``-o max_write=<N>`` option instead.
|
| |
|
|
|
|
| |
Fixes #50.
|
|
|
|
| |
Makes the code much shorter :-).
|
| |
|
| |
|
| |
|
| |
|
|
|