| Commit message (Collapse) | Author | Age |
|
|
|
| |
When running under Valgrind, we otherwise get sporadic test failures.
|
|
|
|
|
| |
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.
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
If we don't assign a value to padding, we get a warning about reading
uninitialized data when sending the iovec to the kernel.
|
| |
| |
| |
| | |
For --help and --version, it returns -1.
|
|/
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
This is an overlooked artifact of the fuse_ll-fuse_session merge.
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
This merge merges struct fuse_ll into struct fuse_session. Since
there is always a one-to-one correspondence between the two,
there is little reason to keep them separate. By merging them,
we save pointers and lines of code.
|
| |
| |
| |
| | |
Replaced "req->se" with "f" where the latter is already defined.
|
| |
| |
| |
| |
| | |
Remove pointless aliasing of "struct fuse_session *se" to "struct
fuse_session *f".
|
| |
| |
| |
| | |
Fixup cuse_lowlevel_new().
|
| |
| |
| |
| | |
Fixup fuse_session_new().
|
| |
| |
| |
| | |
Merge fuse_ll_destroy() and fuse_session_destroy().
|
| |
| |
| |
| | |
Replace se->f with se.
|
| |
| |
| |
| | |
Replaced all references to req->f with req->se.
|
|/
|
|
|
| |
Merged the structures, and replaced fuse_ll with fuse_session
in all type definitions.
|
|
|
|
|
| |
We also accept a number of mount options that are common to
all file systems (nosuid, nodev, ro, etc).
|
| |
|
|\
| |
| |
| |
| | |
Commit e4015aca9b7 already fixed this problem in a different way, so
this is effectively a null-merge.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We have to store the channel before removing it from the session,
otherwise we cannot use it to do the unmount.
This problem was introduced in commit 5698ee09cf7.
Thanks to Michael Theall for reporting & debugging this.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a code simplification patch.
- It confines most of the implementation channel implementation into
fuse_loop_mt (which is its only user).
- It makes it more obvious in the code that channels are only ever used
when using -o clone_fd and multi-threaded main loop.
- It simplies the definition of both struct fuse_session and struct
fuse_chan.
- Theoretically it should result in (minuscule) performance
improvements when not using -o clone_fd.
- Overall, it removes a lot more lines of source code than it adds :-).
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In theory, a poll handle could hang around much longer than the worker
thread that creates it. Furthermore, the thread that created the
pollhandle is no more likely to call fuse_lowlevel_notify_poll() than
any other thread.
In theory, this would have kept the channel alive for much longer than
necessary. In practice, there seems to have been a bug that prevented
this - and instead allowed the channel to be destroyed while there
was still a pollhandle referring to it.
Instead of fixing this by calling fuse_chan_get() and fuse_chan_put() in
do_poll() and fuse_pollhandle_destroy(), we simply transmit poll
notifications over the master channel now.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Fixes #50.
|
| |
| |
| |
| | |
Makes the code much shorter :-).
|
| |
| |
| |
| | |
Fixes #59.
|
| |
| |
| |
| | |
Fixes #67.
|
| |
| |
| |
| |
| |
| | |
This distinction no longer makes sens. fuse_lowlevel.c already contains
several session related functions, and fuse_session.c contains various
stuff that is more related to the channel interface.
|
| |
| |
| |
| | |
There is no point in having a separate file for a 10 line function.
|
| |
| |
| |
| |
| | |
This should make more clear what file contains code for what
purpose.
|