aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* tst_link(): add more assertionsGravatar Nikolaus Rath2017-05-25
| | | | Hopefully this helps debugging issue #157.
* Remove fuse_fs_fgetattr and fuse_fs_ftruncate from linker scriptGravatar pablomh2017-05-25
| | | They were removed from source here: https://github.com/libfuse/libfuse/commit/73b6ff4b75cf1228ea61262c293fcb2fda5dfeea
* Travis-CI: Don't abort on first failed testGravatar Nikolaus Rath2017-05-24
| | | | This should help debugging issue #157.
* Added tst_open_read()Gravatar Nikolaus Rath2017-05-24
| | | | | Slightly increases coverage of examples/passthrough_ll.c (which supports open for reading, but not for writing).
* lib/meson.build: don't crash if there's no libdlGravatar Nikolaus Rath2017-05-24
| | | | | | For example, FreeBSD doesn't have it. Fixes: #173.
* fuse_signals.c: use new do_nothing function instead of SIG_IGNGravatar Nikolaus Rath2017-05-24
| | | | Fixes: #160.
* Released libfuse 3.0.2Gravatar Nikolaus Rath2017-05-24
|
* Make tests build on bsdGravatar Brian Naylor2017-05-24
|
* make buffer size match kernel max transfer sizeGravatar Carlos Maiolino2017-04-20
| | | | | | | | | | | | | | | Currently libfuse has a hardcoded buffer limit to 128kib, while fuse kernel module has a limit up to 32 pages. This patch changes buffer limit to match the current page size, instead of assuming 4096 bytes pages, enabling architectures with bigger pages to use larger buffers, improving performance. Also, add a new macro (HEADER_SIZE) to specify the space needed to accommodate the header, making it easier to understand why those extra 4096 bytes are needed Signed-off-by: Carlos Maiolino <cmaiolino-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
* Set default options before parsingGravatar Tej Chajed2017-04-14
|
* Improved documentation of fuse_context.private_dataGravatar Nikolaus Rath2017-04-12
| | | | | | | | | | In particular, don't call it "user_data" in one place and "private_data" elsewhere. Changing the name of the variable in the prototype should not affect backwards compatibility. Fixes: #155.
* Released 3.0.1Gravatar Nikolaus Rath2017-04-10
|
* Fix travis build script. Broken in e372d.Gravatar Nikolaus Rath2017-04-10
|
* Added ChangeLog for commits c24cc to eb972.Gravatar Nikolaus Rath2017-04-10
|
* Remove 'tests' target in favor of calling py.test directly.Gravatar Nikolaus Rath2017-04-10
| | | | Together with the previous commit, this fixes #156.
* Build tests by default.Gravatar Nikolaus Rath2017-04-10
|
* Only build test/*.py if out of date.Gravatar Nikolaus Rath2017-04-10
|
* Actually test passthrough* examplesGravatar Nikolaus Rath2017-04-07
| | | | | | | | Since os.path.join() interprets leading slashes, we were actually never accessing the mountpoint and doing all the tests in the source directory. Fixes: #139
* passthrough: implemented create()Gravatar Nikolaus Rath2017-04-07
| | | | | | This allows calls like open(file, O_CREAT|O_RDONLY, 0200) which would otherwise fail because we cannot open the file after mknod() has created it with 0200 permissions.
* example/passthrough: use fi->fh for read, write, fallocateGravatar Nikolaus Rath2017-04-07
| | | | | No reason not to use it. May even be a little faster and will consume less resources :-).
* passthrough:truncate(): work on file descriptor when possibleGravatar Nikolaus Rath2017-04-07
| | | | | This allows truncating an open file even if write permission was removed after open() (which is the expected behavior).
* example/passthrough: close open files in release()Gravatar Nikolaus Rath2017-04-07
| | | | That way we can use the file descriptor for other operations.
* passthrough, passthrough_fh: disable attribute cachingGravatar Nikolaus Rath2017-04-07
| | | | Required for better hardlink handling, see comments in patch.
* test_examples(): test without debug messages firstGravatar Nikolaus Rath2017-04-07
| | | | | That way, we are not drowning in messages when a test would also fail without debugging enabled.
* test_examples(): avoid false positives from fuse debug outputGravatar Nikolaus Rath2017-04-07
|
* passthrough_ll: only test functions that are actually providedGravatar Nikolaus Rath2017-04-07
| | | | | | This appeared to work because of an unrelated bug that caused us to actually never access the mountpoint at all and do all tests on the lower filesystem. This issue will be fixed in a separate commit.
* Fix rst markup.Gravatar Nikolaus Rath2017-04-07
|
* Document true meaning of the 'use_ino' option.Gravatar Nikolaus Rath2017-04-07
|
* Remove checked_unlink()Gravatar Nikolaus Rath2017-04-07
| | | | | There is no reason why so many tests require the file system to support unlink() and/or rmdir().
* Turn tst_mknod() into tst_create()Gravatar Nikolaus Rath2017-04-07
| | | | | Ensure that we are really creating a new file. Don't attempt to write, we do that in tst_open_write().
* Renamed tst_write() to tst_open_write()Gravatar Nikolaus Rath2017-04-07
| | | | | We are actually testing both opening of an existing file and writing to it.
* Added tst_unlink()Gravatar Nikolaus Rath2017-04-07
| | | | To check for unlink() support without requiring create()/mknod().
* tst_mkdir(): factor out tst_rmdir()Gravatar Nikolaus Rath2017-04-07
| | | | | This allows testing a filesystem that offers mkdir(), but no rmdir() (and vice versa).
* Rename tst_unlink() to tst_open_unlink()Gravatar Nikolaus Rath2017-04-07
| | | | | This makes more sense, since we are specifically checking unlinking of an open file.
* tst_readdir(): don't require create/mkdir supportGravatar Nikolaus Rath2017-04-07
| | | | | | By creating the files in the lower filesystem, we can test readdir() even for filesystems that don't implement create() or mkdir().
* passthrough_ll: document that functionality is restrictedGravatar Nikolaus Rath2017-04-07
|
* hello.c: don't use constant instead of magic numberGravatar guraga2017-03-28
|
* Document that -o auto_unmount implies -o nodev,nosuidGravatar Nikolaus Rath2017-03-16
| | | | See also issue #148.
* meson.build(): don't use absolute path for include_dir()Gravatar Nikolaus Rath2017-03-15
| | | | No longer supported in Meson 0.39.
* passthrough_fh: declare support for . and .. lookups.Gravatar Nikolaus Rath2017-03-15
|
* open(): fix documentation of O_TRUNC flagGravatar Nikolaus Rath2017-03-15
| | | | | The FUSE_CAP_ATOMIC_IO_TRUNC capability is enabled by default, but we didn't update the open() documentation accordingly.
* Document minimum required Meson version.Gravatar Nikolaus Rath2017-03-15
| | | | Fixes #138.
* Optimize fuse_fs_read. (#145)Gravatar amosonn2017-03-03
| | | Redundant copy when only op.read is available removed.
* Put -Werror in mesonconf, not CFLAGSGravatar Nikolaus Rath2017-01-23
| | | | Putting it in CFLAGS interferes with feature detection.
* Pass _GNU_SOURCE as compiler argumentGravatar Nikolaus Rath2017-01-23
| | | | | Defining it in the file causes trouble because Meson sometimes inserts includes before the first line.
* Only use valgrind if requested explicitly + enable address sanitizerGravatar Nikolaus Rath2017-01-12
|
* Switch Travis build to Meson+NinjaGravatar Nikolaus Rath2017-01-12
|
* Added experimental support for building with Meson+NinjaGravatar Nikolaus Rath2017-01-12
|
* Replaced evil pointer magic with offsetof()Gravatar Nikolaus Rath2017-01-12
| | | | This triggered undefined behaviour warnings from UBSan.
* Rephrased security informationGravatar Nikolaus Rath2017-01-12
| | | | | | | | | | | | The permission caching bug has been present forever, is presumably going to stay around for a while, and is of less concern if allow_other is not used. Since allow_other is disabled by default, I think we can safely make this warning less prominent and document the problem when we describe allow_other. Also, drop the travis build status. It's confusing when reading README.md after extracting the tarball, and I am not sure who benefits from the build status when it is shown on GitHub either.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-23 03:15:20 +0000