fK`NSrSSKrSSKrSSKrSSKJrJrJrJrJ r J r J r \"S\ 5r \"S\5r\"S\ 5r\"S\ 5r\"S\ 5r\"S \5r\(aSS KJrJrJrJrJrJrJr OSrS S /r\R:"\5rS \S\4S\S\44Sjr "SS 5r!g)u _pyfuse3.py Pure-Python components of pyfuse3. Copyright © 2018 Nikolaus Rath This file is part of pyfuse3. This work may be distributed under the terms of the GNU LGPL. N) TYPE_CHECKINGAnyCallableNewTypeOptionalSequenceTuple FileHandleT FileNameTFlagTInodeTModeT XAttrNameT)EntryAttributesFileInfo FUSEError ReaddirTokenRequestContext SetattrFields StatvfsData Operations async_wrapperfn.returncF^[R"T5U4Sj5nU$)Nc2># T"U0UD6IShvN gN7f)N)argskwargsrs 2/usr/lib/python3/dist-packages/pyfuse3/_pyfuse3.pywrapperasync_wrapper..wrapper+s$!&!!!s ) functoolswraps)rr!s` r rr*s#__R"" Nc`\rSrSr%SrSr\\S'Sr\\S'Sr \\S'SIS jr S \ S \ S SSS4Sjr S\\\ \4SS 4SjrS\ S SSS4SjrS\ SSSSS\\S SSS4 SjrS\ S SS\ 4SjrS \ S \ S\S\S SSS4 SjrS \ S \ S\S SSS4 SjrS \ S \ S SSS 4SjrS \ S \ S SSS 4S jrS \ S \ S!\ S SSS4 S"jrS#\ S$\S%\ S&\S'\S SSS 4S(jrS\ S)\ S*\ S SSS4 S+jr S\ S'\S SSS,4S-jr!S\S.\S/\S\"4S0jr#S\S.\S1\"S\4S2jr$S\SS 4S3jr%S\SS 4S4jr&S\S5\SS 4S6jr'S\ S SS\4S7jr(S\S8\S9S:SS 4S;jr)S\SS 4S<jr*S\S5\SS 4S=jr+SJS>jr,SIS?jr-S\ S \.S@\"S SSS 4 SAjr/S\ S \.S SS\"4SBjr0S\ S SS\\.4SCjr1S\ S \.S SSS 4SDjr2S\ S\S SS\4SEjr3S \ S \ S\S'\S SS\SF4 SGjr4SHr5g )Kr1a This class defines the request handler methods that an pyfuse3 file system may implement. If a particular request handler has not been implemented, it must raise `FUSEError` with an errorcode of `errno.ENOSYS`. Further requests of this type will then be handled directly by the FUSE kernel module without calling the handler again. The only exception that request handlers are allowed to raise is `FUSEError`. This will cause the specified errno to be returned by the syscall that is being handled. It is recommended that file systems are derived from this class and only overwrite the handlers that they actually implement. (The methods defined in this class all just raise ``FUSEError(ENOSYS)`` or do nothing). Tsupports_dot_lookupFenable_writeback_cache enable_aclrNcg)zInitialize operations. This method will be called just before the file system starts handling requests. It must not raise any exceptions (not even `FUSEError`), since it is not handling a particular client request. Nr)selfs r initOperations.initFs r% parent_inodenamectxrrc<# [[R5e7f)aLook up a directory entry by name and get its attributes. This method should return an `EntryAttributes` instance for the directory entry *name* in the directory with inode *parent_inode*. If there is no such entry, the method should either return an `EntryAttributes` instance with zero ``st_ino`` value (in which case the negative lookup will be cached as specified by ``entry_timeout``), or it should raise `FUSEError` with an errno of `errno.ENOENT` (in this case the negative result will not be cached). *ctx* will be a `RequestContext` instance. The file system must be able to handle lookups for :file:`.` and :file:`..`, no matter if these entries are returned by `readdir` or not. (Successful) execution of this handler increases the lookup count for the returned inode by one. rerrnoENOSYSr,r/r0r1s r lookupOperations.lookupPs4 %% inode_listc # g7f)a[Decrease lookup counts for inodes in *inode_list*. *inode_list* is a list of ``(inode, nlookup)`` tuples. This method should reduce the lookup count for each *inode* by *nlookup*. If the lookup count reaches zero, the inode is currently not known to the kernel. In this case, the file system will typically check if there are still directory entries referring to this inode and, if not, remove the inode. If the file system is unmounted, it may not have received `forget` calls to bring all lookup counts to zero. The filesystem needs to take care to clean up inodes that at that point still have non-zero lookup count (e.g. by explicitly calling `forget` with the current lookup count for every such inode after `main` has returned). This method must not raise any exceptions (not even `FUSEError`), since it is not handling a particular client request. Nr)r,r:s r forgetOperations.forgetls 0 sinodec<# [[R5e7f)zGet attributes for *inode*. *ctx* will be a `RequestContext` instance. This method should return an `EntryAttributes` instance with the attributes of *inode*. The `~EntryAttributes.entry_timeout` attribute is ignored in this context. r3r,r>r1s r getattrOperations.getattr %%r9attrfieldsrfhc<# [[R5e7f)aChange attributes of *inode*. *fields* will be an `SetattrFields` instance that specifies which attributes are to be updated. *attr* will be an `EntryAttributes` instance for *inode* that contains the new values for changed attributes, and undefined values for all other attributes. Most file systems will additionally set the `~EntryAttributes.st_ctime_ns` attribute to the current time (to indicate that the inode metadata was changed). If the syscall that is being processed received a file descriptor argument (like e.g. :manpage:`ftruncate(2)` or :manpage:`fchmod(2)`), *fh* will be the file handle returned by the corresponding call to the `open` handler. If the syscall was path based (like e.g. :manpage:`truncate(2)` or :manpage:`chmod(2)`), *fh* will be `None`. *ctx* will be a `RequestContext` instance. The method should return an `EntryAttributes` instance (containing both the changed and unchanged values). r3)r,r>rDrErFr1s r setattrOperations.setattrs@ %%r9c<# [[R5e7f)zTReturn target of symbolic link *inode*. *ctx* will be a `RequestContext` instance. r3r@s r readlinkOperations.readlinks %%r9moderdevc<# [[R5e7f)aCreate (possibly special) file. This method must create a (special or regular) file *name* in the directory with inode *parent_inode*. Whether the file is special or regular is determined by its *mode*. If the file is neither a block nor character device, *rdev* can be ignored. *ctx* will be a `RequestContext` instance. The method must return an `EntryAttributes` instance with the attributes of the newly created directory entry. (Successful) execution of this handler increases the lookup count for the returned inode by one. r3)r,r/r0rMrNr1s r mknodOperations.mknods. %%r9c<# [[R5e7f)aCreate a directory. This method must create a new directory *name* with mode *mode* in the directory with inode *parent_inode*. *ctx* will be a `RequestContext` instance. This method must return an `EntryAttributes` instance with the attributes of the newly created directory entry. (Successful) execution of this handler increases the lookup count for the returned inode by one. r3)r,r/r0rMr1s r mkdirOperations.mkdir( %%r9c<# [[R5e7f)aVRemove a (possibly special) file. This method must remove the (special or regular) file *name* from the direcory with inode *parent_inode*. *ctx* will be a `RequestContext` instance. If the inode associated with *file* (i.e., not the *parent_inode*) has a non-zero lookup count, or if there are still other directory entries referring to this inode (due to hardlinks), the file system must remove only the directory entry (so that future calls to `readdir` for *parent_inode* will no longer include *name*, but e.g. calls to `getattr` for *file*'s inode still succeed). (Potential) removal of the associated inode with the file contents and metadata must be deferred to the `forget` method to be carried out when the lookup count reaches zero (and of course only if at that point there are no more directory entries associated with the inode either). r3r6s r unlinkOperations.unlinks0 %%r9c<# [[R5e7f)aRemove directory *name*. This method must remove the directory *name* from the direcory with inode *parent_inode*. *ctx* will be a `RequestContext` instance. If there are still entries in the directory, the method should raise ``FUSEError(errno.ENOTEMPTY)``. If the inode associated with *name* (i.e., not the *parent_inode*) has a non-zero lookup count, the file system must remove only the directory entry (so that future calls to `readdir` for *parent_inode* will no longer include *name*, but e.g. calls to `getattr` for *file*'s inode still succeed). Removal of the associated inode holding the directory contents and metadata must be deferred to the `forget` method to be carried out when the lookup count reaches zero. (Since hard links to directories are not allowed by POSIX, this method is not required to check if there are still other directory entries refering to the same inode. This conveniently avoids the ambigiouties associated with the ``.`` and ``..`` entries). r3r6s r rmdirOperations.rmdir s6 %%r9targetc<# [[R5e7f)aCreate a symbolic link. This method must create a symbolink link named *name* in the directory with inode *parent_inode*, pointing to *target*. *ctx* will be a `RequestContext` instance. The method must return an `EntryAttributes` instance with the attributes of the newly created directory entry. (Successful) execution of this handler increases the lookup count for the returned inode by one. r3)r,r/r0r\r1s r symlinkOperations.symlink*rUr9parent_inode_oldname_oldparent_inode_newname_newflagsc<# [[R5e7f)a#Rename a directory entry. This method must rename *name_old* in the directory with inode *parent_inode_old* to *name_new* in the directory with inode *parent_inode_new*. If *name_new* already exists, it should be overwritten. *flags* may be `RENAME_EXCHANGE` or `RENAME_NOREPLACE`. If `RENAME_NOREPLACE` is specified, the filesystem must not overwrite *name_new* if it exists and return an error instead. If `RENAME_EXCHANGE` is specified, the filesystem must atomically exchange the two files, i.e. both must exist and neither may be deleted. *ctx* will be a `RequestContext` instance. Let the inode associated with *name_old* in *parent_inode_old* be *inode_moved*, and the inode associated with *name_new* in *parent_inode_new* (if it exists) be called *inode_deref*. If *inode_deref* exists and has a non-zero lookup count, or if there are other directory entries referring to *inode_deref*), the file system must update only the directory entry for *name_new* to point to *inode_moved* instead of *inode_deref*. (Potential) removal of *inode_deref* (containing the previous contents of *name_new*) must be deferred to the `forget` method to be carried out when the lookup count reaches zero (and of course only if at that point there are no more directory entries associated with *inode_deref* either). r3)r,r`rarbrcrdr1s r renameOperations.rename@sL %%r9new_parent_inodenew_namec<# [[R5e7f)aCCreate directory entry *name* in *parent_inode* refering to *inode*. *ctx* will be a `RequestContext` instance. The method must return an `EntryAttributes` instance with the attributes of the newly created directory entry. (Successful) execution of this handler increases the lookup count for the returned inode by one. r3)r,r>rhrir1s r linkOperations.linkhs$ %%r9rc<# [[R5e7f)axOpen a inode *inode* with *flags*. *ctx* will be a `RequestContext` instance. *flags* will be a bitwise or of the open flags described in the :manpage:`open(2)` manpage and defined in the `os` module (with the exception of ``O_CREAT``, ``O_EXCL``, ``O_NOCTTY`` and ``O_TRUNC``) This method must return a `FileInfo` instance. The `FileInfo.fh` field must contain an integer file handle, which will be passed to the `read`, `write`, `flush`, `fsync` and `release` methods to identify the open file. The `FileInfo` instance may also have relevant configuration attributes set; see the `FileInfo` documentation for more information. r3)r,r>rdr1s r openOperations.open|* %%r9offsizec<# [[R5e7f)aRead *size* bytes from *fh* at position *off*. *fh* will be an integer filehandle returned by a prior `open` or `create` call. This function should return exactly the number of bytes requested except on EOF or error, otherwise the rest of the data will be substituted with zeroes. r3)r,rFrqrrs r readOperations.read  %%r9bufc<# [[R5e7f)aPWrite *buf* into *fh* at *off*. *fh* will be an integer filehandle returned by a prior `open` or `create` call. This method must return the number of bytes written. However, unless the file system has been mounted with the ``direct_io`` option, the file system *must* always write *all* the provided data (i.e., return ``len(buf)``). r3)r,rFrqrws r writeOperations.writes" %%r9c<# [[R5e7f)a Handle close() syscall. *fh* will be an integer filehandle returned by a prior `open` or `create` call. This method is called whenever a file descriptor is closed. It may be called multiple times for the same open file (e.g. if the file handle has been duplicated). r3r,rFs r flushOperations.flushrCr9c<# [[R5e7f)a"Release open file. This method will be called when the last file descriptor of *fh* has been closed, i.e. when the file is no longer opened by any client process. *fh* will be an integer filehandle returned by a prior `open` or `create` call. Once `release` has been called, no future requests for *fh* will be received (until the value is re-used in the return value of another `open` or `create` call). This method may return an error by raising `FUSEError`, but the error will be discarded because there is no corresponding client request. r3r|s r releaseOperations.release& %%r9datasyncc<# [[R5e7f)zFlush buffers for open file *fh*. If *datasync* is true, only the file contents should be flushed (in contrast to the metadata about the file). *fh* will be an integer filehandle returned by a prior `open` or `create` call. r3r,rFrs r fsyncOperations.fsyncrCr9c<# [[R5e7f)zOpen the directory with inode *inode*. *ctx* will be a `RequestContext` instance. This method should return an integer file handle. The file handle will be passed to the `readdir`, `fsyncdir` and `releasedir` methods to identify the directory. r3r@s r opendirOperations.opendirrCr9start_idtokenrc<# [[R5e7f)aRead entries in open directory *fh*. This method should list the contents of directory *fh* (as returned by a prior `opendir` call), starting at the entry identified by *start_id*. Instead of returning the directory entries directly, the method must call `readdir_reply` for each directory entry. If `readdir_reply` returns True, the file system must increase the lookup count for the provided directory entry by one and call `readdir_reply` again for the next entry (if any). If `readdir_reply` returns False, the lookup count must *not* be increased and the method should return without further calls to `readdir_reply`. The *start_id* parameter will be either zero (in which case listing should begin with the first entry) or it will correspond to a value that was previously passed by the file system to the `readdir_reply` function in the *next_id* parameter. If entries are added or removed during a `readdir` cycle, they may or may not be returned. However, they must not cause other entries to be skipped or returned more than once. :file:`.` and :file:`..` entries may be included but are not required. However, if they are reported the filesystem *must not* increase the lookup count for the corresponding inodes (even if `readdir_reply` returns True). r3)r,rFrrs r readdirOperations.readdirsD %%r9c<# [[R5e7f)zRelease open directory. This method will be called exactly once for each `opendir` call. After *fh* has been released, no further `readdir` requests will be received for it (until it is opened again with `opendir`). r3r|s r releasedirOperations.releasedir! %%r9c<# [[R5e7f)zFlush buffers for open directory *fh*. If *datasync* is true, only the directory contents should be flushed (in contrast to metadata about the directory itself). r3rs r fsyncdirOperations.fsyncdir.rr9c<# [[R5e7f)zGet file system statistics. *ctx* will be a `RequestContext` instance. The method must return an appropriately filled `StatvfsData` instance. r3)r,r1s r statfsOperations.statfs;rr9c SSKnSSKnSSKJn [ 5nUR 5R 5H~upVURSU35 URU5HPupxpURU"U5SUSU 35 U (dM.URSU R535 MR M [RSRU55 g) aAsynchronous debugging. This method will be called when the ``fuse_stacktrace`` extended attribute is set on the mountpoint. The default implementation logs the current stack trace of every running Python thread. This can be quite useful to debug file system deadlocks. rN)basenamez # ThreadID: :z, in z  ) sys tracebackos.pathrlist_current_framesitemsappend extract_stackstriplogerrorjoin) r,rrrcodethreadIdframefilenamelinenor0lines r stacktraceOperations.stacktraceHs $v"224::r0rr1s r setxattrOperations.setxattr_rvr9c<# [[R5e7f)aReturn extended attribute *name* of *inode*. *ctx* will be a `RequestContext` instance. If the attribute does not exist, the method must raise `FUSEError` with an error code of `ENOATTR`. *name* will be of type `bytes`, but is guaranteed not to contain zero-bytes (``\0``). r3r,r>r0r1s r getxattrOperations.getxattrq %%r9c<# [[R5e7f)zGet list of extended attributes for *inode*. *ctx* will be a `RequestContext` instance. This method must return a sequence of `bytes` objects. The objects must not include zero-bytes (``\0``). r3r@s r listxattrOperations.listxattrs %%r9c<# [[R5e7f)aRemove extended attribute *name* of *inode*. *ctx* will be a `RequestContext` instance. If the attribute does not exist, the method must raise `FUSEError` with an error code of `ENOATTR`. *name* will be of type `bytes`, but is guaranteed not to contain zero-bytes (``\0``). r3rs r removexattrOperations.removexattrrr9c<# [[R5e7f)a.Check if requesting process has *mode* rights on *inode*. *ctx* will be a `RequestContext` instance. The method must return a boolean value. If the ``default_permissions`` mount option is given, this method is not called. When implementing this method, the `get_sup_groups` function may be useful. r3)r,r>rMr1s r accessOperations.accessrr9)rrc<# [[R5e7f)aCreate a file with permissions *mode* and open it with *flags*. *ctx* will be a `RequestContext` instance. The method must return a tuple of the form *(fi, attr)*, where *fi* is a FileInfo instance handle like the one returned by `open` and *attr* is an `EntryAttributes` instance with the attributes of the newly created directory entry. (Successful) execution of this handler increases the lookup count for the returned inode by one. r3)r,r/r0rMrdr1s r createOperations.createrpr9r)rN)r1rrr)6__name__ __module__ __qualname____firstlineno____doc__r(bool__annotations__r)r*r-r r r7rr intr<rArr rHrKrrPrSrWrZr^strr rfrkrnbytesrtryr}rrrrrrrrrrrrrrr__static_attributes__rr%r rr1s !%$#(D(J &&& &  &8 U63;/0   4&&&  & & &  & & [ ! &  &  &D & & &  &&&& &  &  & &2&&& &  &  &,&&& &  &4&&& &  &:&&& &  &  &,&& &&&&! &&  &&  &&&& &&P&&!& &  &  &(&&& &  &.& && &  &$& && & &&& & & & & &*& &&  & &&&  & "& "&"& "&  "&H &  &  & &  & &  & &  &  &#.&&& &  &  &$&&& &  &" & & & *  &&&& &  &"&&& &  &*&&& &  &  & , -&r%)"rr4r#loggingtypingrrrrrrr rr rr r r rrpyfuse3rrrrrrr__all__ getLoggerrrrrrr%r rs  mS) K '  3  \5 ) EEEI  ) ! hsCx(Xc3h-?[ &[ &r%