Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/lib/libperfuse/debug.c

104 lines
3.1 KiB
C
Raw Normal View History

- Correctly handle rename whith overwritten destination - Keep track of file name to avoid lookups when we can. This makes sure we do not have two cookies for the same inode, a situation that cause wreak havoc when we come to remove or rename a node. - Do not use PUFFS_FLAG_BUILDPATH at all, since we now track file names - In open, queue requests after checking for access, as there is no merit to queue a will-be-denied request while we can deny it immediatly - request reclaim of removed nodes at inactive stage
2010-10-03 09:46:47 +04:00
/* $NetBSD: debug.c,v 1.5 2010/10/03 05:46:47 manu Exp $ */
libperfuse(3) is a PUFFS relay to FUSE. In order to use it, FUSE filesystem must be patched to #include <perfuse.h> in the source files that open /dev/fuse and perform the mount(2) system call. The FUSE filesystem must be linked with -lperfuse. libperfuse(3) implements the FUSE kernel interface, on which libfuse or any FUSE filesystem that opens /dev/fuse directly can be used. For now, an external daemon called perfused(8) is used. This may change in the future.
2010-08-25 11:16:00 +04:00
/*-
* Copyright (c) 2010 Emmanuel Dreyfus. All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions
* are met:
* 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer.
* 2. Redistributions in binary form must reproduce the above copyright
* notice, this list of conditions and the following disclaimer in the
* documentation and/or other materials provided with the distribution.
*
* THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS
* ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
* TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
* PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS
* BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
* POSSIBILITY OF SUCH DAMAGE.
*/
#include <puffs.h>
#include <sys/types.h>
#include "perfuse_if.h"
#include "fuse.h"
struct perfuse_opcode {
int opcode;
const char *opname;
};
const struct perfuse_opcode perfuse_opcode[] = {
{ FUSE_LOOKUP, "LOOKUP" },
{ FUSE_FORGET, "FORGET" },
{ FUSE_GETATTR, "GETATTR" },
{ FUSE_SETATTR, "SETATTR" },
{ FUSE_READLINK, "READLINK" },
{ FUSE_SYMLINK, "SYMLINK" },
{ FUSE_MKNOD, "MKNOD" },
{ FUSE_MKDIR, "MKDIR" },
{ FUSE_UNLINK, "UNLINK" },
{ FUSE_RMDIR, "RMDIR" },
{ FUSE_RENAME, "RENAME" },
{ FUSE_LINK, "LINK" },
{ FUSE_OPEN, "OPEN" },
{ FUSE_READ, "READ" },
{ FUSE_WRITE, "WRITE" },
{ FUSE_STATFS, "STATFS" },
{ FUSE_RELEASE, "RELEASE" },
{ FUSE_FSYNC, "FSYNC" },
{ FUSE_SETXATTR, "SETXATTR" },
{ FUSE_GETXATTR, "GETXATTR" },
{ FUSE_LISTXATTR, "LISTXATTR" },
{ FUSE_REMOVEXATTR, "REMOVEXATTR" },
{ FUSE_FLUSH, "FLUSH" },
{ FUSE_INIT, "INIT" },
{ FUSE_OPENDIR, "OPENDIR" },
{ FUSE_READDIR, "READDIR" },
{ FUSE_RELEASEDIR, "RELEASEDIR" },
{ FUSE_FSYNCDIR, "FSYNCDIR" },
{ FUSE_GETLK, "GETLK" },
{ FUSE_SETLK, "SETLK" },
{ FUSE_SETLKW, "SETLKW" },
{ FUSE_ACCESS, "ACCESS" },
{ FUSE_CREATE, "CREATE" },
{ FUSE_INTERRUPT, "INTERRUPT" },
{ FUSE_BMAP, "BMAP" },
{ FUSE_DESTROY, "DESTROY" },
{ FUSE_IOCTL, "IOCTL" },
{ FUSE_POLL, "POLL" },
{ FUSE_CUSE_INIT, "CUSE_INIT" },
{ 0, "UNKNOWN" },
};
== file close operations == - use PUFFS_KFLAG_WTCACHE to puffs_init so that all writes are immediatly send to the filesystem, and we do not have anymore write after inactive. As a consequence, we can close files at inactive stage, and there is not any concern left with files opened at create time. We also do not have anymore to open ourselves in readdir and fsync. - Fsync on close (inactive stage). That makes sure we will not need to do these operations once the file is closed (FUSE want an open file). short sircuit the request that come after the close, bu not fsinc'ing closed files, - Use PUFFS_KFLAG_IAONDEMAND to get less inactive calls == Removed nodes == - more ENOENT retunred for operations on removed node (but there are probably some still missing): getattr, ooen, setattr, fsync - set PND_REMOVE before sending the UNLINK/RMDIR operations so that we avoid races during UNLINK completion. Also set PND_REMOVED on node we overwirte in rename == Filehandle fixes == - queue open operation to avoid getting two fh for one file - set FH in getattr, if the file is open - Just requires a read FH for fsyncdir, as we always opendir in read mode. Ok, this is misleading :-) == Misc == - do not set FUSE_FATTR_ATIME_NOW in setattr, as we provide the time - short circuit nilpotent operations in setattr - add a filename diagnostic flag to dump file names
2010-09-23 20:02:34 +04:00
const char *perfuse_qtypestr[] = {
"READDIR",
"READ",
"WRITE",
"AFTERWRITE",
- Correctly handle rename whith overwritten destination - Keep track of file name to avoid lookups when we can. This makes sure we do not have two cookies for the same inode, a situation that cause wreak havoc when we come to remove or rename a node. - Do not use PUFFS_FLAG_BUILDPATH at all, since we now track file names - In open, queue requests after checking for access, as there is no merit to queue a will-be-denied request while we can deny it immediatly - request reclaim of removed nodes at inactive stage
2010-10-03 09:46:47 +04:00
"OPEN",
= Open files = - Restore open on our own in fsycn and readdir, as the node may not already be open, and FUSE really wants it to be. No need to close immediatly, it can be done at inactive time. = Write operations = - fix a nasty bug that corrupted files on write (written added twice) - Keep track of file size in order to honour PUFFS_IO_APPEND = many fixes in rename = - handler overwritten nodes correctly - wait for all operations on the node to drain before doing rename, as filesystems may not cope with operations on a moving file. - setback PUFFS_SETBACK_INACT_N1 cannot be used from rename, we therefore miss the inactive time for an overwritten node. This bounds us to give up PUFFS_KFLAG_IAONDEMAND. = Removed files = - forbid most operations on a removed node, return ENOENT - setback PUFFS_SETBACK_NOREF_N1 at inactive stage to cause removed file reclaim = Misc = - Update outdated ARGSUSED for lint - Fix a memory leak (puffs_pn_remove instead of puffs_pn_put) - Do not use PUFFS_FLAG_BUILDPATH except for debug output. It makes the lookup code much simplier.
2010-09-29 12:01:10 +04:00
"AFTERXCHG"
== file close operations == - use PUFFS_KFLAG_WTCACHE to puffs_init so that all writes are immediatly send to the filesystem, and we do not have anymore write after inactive. As a consequence, we can close files at inactive stage, and there is not any concern left with files opened at create time. We also do not have anymore to open ourselves in readdir and fsync. - Fsync on close (inactive stage). That makes sure we will not need to do these operations once the file is closed (FUSE want an open file). short sircuit the request that come after the close, bu not fsinc'ing closed files, - Use PUFFS_KFLAG_IAONDEMAND to get less inactive calls == Removed nodes == - more ENOENT retunred for operations on removed node (but there are probably some still missing): getattr, ooen, setattr, fsync - set PND_REMOVE before sending the UNLINK/RMDIR operations so that we avoid races during UNLINK completion. Also set PND_REMOVED on node we overwirte in rename == Filehandle fixes == - queue open operation to avoid getting two fh for one file - set FH in getattr, if the file is open - Just requires a read FH for fsyncdir, as we always opendir in read mode. Ok, this is misleading :-) == Misc == - do not set FUSE_FATTR_ATIME_NOW in setattr, as we provide the time - short circuit nilpotent operations in setattr - add a filename diagnostic flag to dump file names
2010-09-23 20:02:34 +04:00
};
- Use SOCK_DGRAM instead of SOCK_STREAM, as the filesystem seems to assume datagram semantics: when using SOCK_STREAM, if perfused sends frames faster than the filesystem consumes them, it will grab multiple frames at once and discard anything beyond the first one. For now the code can work both with SOCK_DGRAM and SOCK_STREAM, but SOCK_STREAM support will probably have to be removed for the sake of readability. - Remeber to sync parent directories when moving a node - In debug output, display the requeue type (readdir, write, etc...)
2010-09-15 05:51:43 +04:00
libperfuse(3) is a PUFFS relay to FUSE. In order to use it, FUSE filesystem must be patched to #include <perfuse.h> in the source files that open /dev/fuse and perform the mount(2) system call. The FUSE filesystem must be linked with -lperfuse. libperfuse(3) implements the FUSE kernel interface, on which libfuse or any FUSE filesystem that opens /dev/fuse directly can be used. For now, an external daemon called perfused(8) is used. This may change in the future.
2010-08-25 11:16:00 +04:00
const char *
perfuse_opname(opcode)
int opcode;
{
const struct perfuse_opcode *po;
for (po = perfuse_opcode; po->opcode; po++) {
if (po->opcode == opcode)
return po->opname;
}
return po->opname; /* "UNKNOWN" */
}