| Age | Commit message (Collapse) | Author | Lines |
|---|
|
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.
|
|
No reason not to use it. May even be a little faster and will
consume less resources :-).
|
|
This allows truncating an open file even if write permission
was removed after open() (which is the expected behavior).
|
|
That way we can use the file descriptor for other operations.
|
|
Required for better hardlink handling, see comments in patch.
|
|
|
|
|
|
|
|
|
|
This triggered undefined behaviour warnings from UBSan.
|
|
|
|
|
|
|
|
This reverts commit d5cdbb94a0650b0a462682cf0a84463ff1513900.
null works completely fine, just the mountpoint should
be a regular file -- so there is no need to dismiss it.
Also:
- fixing up compiler warnings
- checking if the mountpoint is a regular file
|
|
|
|
Otherwise building w/o optimization (-O0) fails.
passthrough_ll.c: In function 'lo_readlink':
passthrough_ll.c:251:11: error: 'PATH_MAX' undeclared (first use in this function)
char buf[PATH_MAX + 1];
(gcc v5.3.0 in Alpine Linux v3.4.6 x86_64 w/ musl-libc v1.1.14.)
|
|
If we want to do, what system would do anyway upon program termination,
then let's try to be a bit more scrupulous.
|
|
root lo_inode's next and prev were not set early enough, which led to
accessing addr 0x8 (or 0x4, depending on ptr size) when setting prev
variable in lo_free(lo.root.next), because lo.root.next was NULL.
|
|
"No break at the end of case cuse.c /example line 235 Code Analysis Problem"
|
|
Fixes: #81.
|
|
Modifying struct fuse_config in the init() handler is the canonical way
to adjust file-system implementation specific settings. There is no need
to have flags in struct fuse_operations.
|
|
Several options (use_ino, etc) depend on the file system
implementation. Allowing them to be set from the command line makes no
sense.
|
|
We now only list options that are potentially useful for an
end-user (and unlikely to accidentally break a file system). The full
list of FUSE options has been moved to the documentation of the
fuse_new() and fuse_session_new() functions.
|
|
This obsoletes the ftruncate & fgetattr handlers.
Fixes #58.
|
|
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.
|
|
This option really affects the behavior of the session loop, not the
low-level interface. Therefore, it does not belong in the fuse_session
object.
|
|
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.
|
|
There's now a way to inhibit the "usage" line (which actually got lost
in commit 225c12aebf2d), which makes it easier for simply file-systems
to generate good-looking --help output.
|
|
|
|
An earlier version of the fioclient.c example was intended to be
used together with cusexmp.c. The former has since evolved into
ioctl_client.c and no longer has the function necessary to test
CUSE. Therefore, we've added a new cuse_client.c that is clearly
associated with the cuse.c example file system.
|
|
I think this is the reason for a sporadic test failure, where
fuse_lowlevel_notify_store() fails.
|
|
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.
|
|
The current behavior makes it difficult to add help for
additional options. With the change, this becomes a lot easier.
|
|
|
|
This does not seem to be working. Maybe because it tries to treat the
mountpoint as a file rather than a directory?
|
|
Fixes #32.
|
|
|
|
|
|
These examplesdemonstrate the use of the `fuse_lowlevel_notify_store`
and `fuse_lowlevel_notify_inval_inode` functions.
|
|
Help and version messages can be generated using the new
fuse_lowlevel_help(), fuse_lowlevel_version(), fuse_mount_help(), and
fuse_mount_version() functions.
The fuse_parse_cmdline() function has been made more powerful
to do this automatically, and is now explicitly intended only
for low-level API users.
This is a code simplication patch. We don't have to parse for --help and
--version in quite as many places, and we no longer have a low-level
initialization function be responsible for the (super-high level) task
of printing a program usage message.
In the high-level API, we can now handle the command line parsing
earlier and avoid running other initialization code if we're just going
to abort later on.
|
|
|
|
The only struct fuse_chan that's accessible to the user application is
the "master" channel that is returned by fuse_mount and stored in struct
fuse_session.
When using the multi-threaded main loop with the "clone_fd" option, each
worker thread gets its own struct fuse_chan. However, none of these are
available to the user application, nor do they hold references to struct
fuse_session (the pointer is always null).
Therefore, any presence of struct fuse_chan can be removed
without loss of functionality by relying on struct fuse_session instead.
This reduces the number of API functions and removes a potential source
of confusion (since the new API no longer looks as if it might be
possible to add multiple channels to one session, or to share one
channel between multiple sessions).
Fixes issue #17.
|
|
|
|
|
|
Fixes issue #39.
|
|
|
|
See renameat2() system call in linux-3.15 and later kernels.
|
