summaryrefslogtreecommitdiffstats
path: root/sys/miscfs (follow)
Commit message (Collapse)AuthorAgeFilesLines
* make some `struct vops' members explicitly NULL instead of implicitly NULLsemarie2021-03-242-2/+5
| | | | ok mpi@
* spellingjsg2021-03-112-6/+6
|
* Replace SB_KNOTE and sb_flagsintr with direct checking of klist.visa2021-01-171-6/+1
| | | | OK mpi@ as part of a larger diff
* Refactor klist insertion and removalvisa2020-12-253-10/+10
| | | | | | | | | | | | Rename klist_{insert,remove}() to klist_{insert,remove}_locked(). These functions assume that the caller has locked the klist. The current state of locking remains intact because the kernel lock is still used with all klists. Add new functions klist_insert() and klist_remove() that lock the klist internally. This allows some code simplification. OK mpi@
* Convert fusefs_sysctl to sysctl_bounded_argsgnezdo2020-11-171-21/+12
| | | | OK millert@
* Implement a simple kqfilter for deadfs matching its poll handler.mpi2020-06-151-1/+21
| | | | ok visa@, millert@
* Set __EV_HUP when the conditions matching poll(2)'s POLLUP are found.mpi2020-06-151-1/+5
| | | | | | This is only done in poll-compatibility mode, when __EV_POLL is set. ok visa@, millert@
* Rename poll-compatibility flag to better reflect what it is.mpi2020-06-111-2/+2
| | | | | | While here prefix kernel-only EV flags with two underbars. Suggested by kettenis@, ok visa@
* Use a new EV_OLDAPI flag to match the behavior of poll(2) and select(2).mpi2020-06-081-1/+4
| | | | | | | | | Adapt FS kqfilters to always return true when the flag is set and bypass the polling mechanism of the NFS thread. While here implement a write filter for NFS. ok visa@
* Use seltrue_kqfilter() instead of hand-rolling it in multiple drivers.mpi2020-05-131-11/+2
| | | | ok visa@
* Make fifo_kqfilter() honor FREAD|FWRITE just like fifo_poll() does.mpi2020-04-081-1/+5
| | | | | | | Prevent generating events that do not correspond to how the fifo has been opened. ok visa@, millert@
* Pass correct socket to the write kqueue filter.mpi2020-04-081-2/+5
| | | | | | Make EVFILT_WRITE notifications on fifo work. ok visa@, millert@
* Abstract the head of knote lists. This allows extending the lists,visa2020-04-073-12/+12
| | | | | | for example, with locking assertions. OK mpi@, anton@
* Return POLLERR instead of EINVAL in fusepoll().mpi2020-04-031-2/+2
| | | | ok kettenis@
* Replace field f_isfd with field f_flags in struct filterops to allowvisa2020-02-203-10/+10
| | | | | | adding more filter properties without cluttering the struct. OK mpi@, anton@
* struct vops is not modified during runtime so use const which moves eachclaudio2020-01-204-8/+8
| | | | | into read-only data segment. OK deraadt@ tedu@
* Convert infinite sleeps to tsleep_nsec(9).mpi2020-01-081-5/+5
| | | | ok bluhm@
* Use C99 designated initializers with struct filterops. In addition,visa2019-12-313-21/+44
| | | | | | make the structs const so that the data are put in .rodata. OK mpi@, deraadt@, anton@, bluhm@
* Convert struct vfsops initializer to C99 style.bluhm2019-12-261-14/+14
| | | | OK visa@
* Reintroduce socket locking inside socket event filters.visa2019-12-121-3/+11
| | | | | Tested by anton@, sashan@ OK mpi@, anton@, sashan@
* Convert infinite sleeps to tsleep_nsec(9).mpi2019-12-052-4/+4
| | | | ok jca@
* Unlock the vnode in vop_inactive of deadfs. The unlock operation isvisa2019-10-191-2/+12
| | | | | | | a no-op at the moment, but future work will introduce an actual lock that has to be released. OK mpi@ anton@
* Allow concurrent reads of the f_offset field of struct file byanton2019-08-051-2/+2
| | | | | | | | | serializing both read/write operations using the existing file mutex. The vnode lock still grants exclusive write access to the offset; the mutex is only used to make the actual write atomic and prevent any concurrent reader from observing intermediate values. ok mpi@ visa@
* Revert anton@ changes about read/write unlockingsolene2019-07-121-2/+2
| | | | | | https://marc.info/?l=openbsd-cvs&m=156277704122293&w=2 ok anton@
* Make read/write of the f_offset field belonging to struct file MP-safe;anton2019-07-101-2/+2
| | | | | | | | | | | | | | | | as part of the effort to unlock the kernel. Instead of relying on the vnode lock, introduce a dedicated lock per file. Exclusive write access is granted using the new foffset_enter and foffset_leave API. A convenience function foffset_get is also available for threads that only need to read the current offset. The lock acquisition order in vn_write has been changed to match the one in vn_read in order to avoid a potential deadlock. This change also gets rid of a documented race in vn_read(). Inspired by the FreeBSD implementation. With help and ok mpi@ visa@
* Use FNONBLOCK instead of SS_NBIO to check/indicate that the I/O modempi2018-07-301-18/+14
| | | | | | | | | | | | | for sockets is non-blocking. This allows us to G/C SS_NBIO. Having to keep the two flags in sync in a mp-safe way is complicated. This change introduce a behavior change in sosplice(), it can now always block. However this should not matter much due to the socket lock being taken beforhand. ok bluhm@, benno@, visa@
* Replace VATTR_NULL() with memset(3) in fusefs_getattr(). VATTR_NULL()helg2018-07-181-3/+3
| | | | | | | | sets all members of struct vattr to VNOVAL (-1) instead of 0, which is what is appropriate here. The VATTR_NULL() macro is intended for initialising struct vattr when setting attributes. ok mpi@
* Don't send FBT_DESTROY if the FUSE connection is still PENDING. Alsohelg2018-07-171-13/+14
| | | | | | | | | | | don't attempt to determine the size of the root inode. This is because we don't need to know the size of directories and FBT_GETATTR will also cause a deadlock if fuse_unmount(3) is called before the file system has a chance to process fbufs. Add corresponding regression test. ok mpi@
* Insert the appropriate uvm_vnp_uncache(9) and uvm_vnp_setsize(9)helg2018-07-162-4/+40
| | | | | | | kernel calls to ensure that the UVM cache for memory mapped files is up to date. ok mpi@
* Implement FBT_FSYNC, which is called on fsync(2) and fdatasync(2).helg2018-07-162-3/+61
| | | | | | | Currently ignores the a_waitfor argument and always invokes the file system's fsync implementation synchronously. ok mpi@
* Do not leak memory and a fp reference when !root passes `allow_other'.mpi2018-07-051-4/+5
| | | | | | Fix CID 1470236. ok helg@
* Refactor to simplify - no functional change.helg2018-06-271-31/+14
| | | | ok mpi@
* Remove unused fbuf parameter from fuse_device_cleanup().helg2018-06-253-34/+28
| | | | ok mpi@
* Don't timeout on fb_queue(9). The current process will blockhelg2018-06-214-25/+32
| | | | | | | | | | | | | indefinitely and cannot be interrupted or killed. This is consistent with how VFS system calls should behave. If the file system becomes unresponsive then the only sane solution is for the user to kill the file system daemon. Implementing the equivalent of nfs -osoft or -ointr to either timeout or allow the blocking FUSE operation to be interrupted can be considered in a future patch. ok mpi@
* Drop redundant "node == parent node" checks from VOP_RMDIR()visa2018-06-211-10/+1
| | | | | | implementations. Rely on the VFS layer to do the checking. OK mpi@, helg@
* Fix formatting.helg2018-06-201-6/+6
|
* Changes the default mount behaviour so only the user that mounts thehelg2018-06-193-10/+58
| | | | | | | | file system can access it unless the allow_other mount options is specified. The allow_other mount option makes the file system available to other users just like any other mounted file system. ok mpi@
* Send the calling thread id, effective uid and gid, and umask to thehelg2018-06-191-1/+11
| | | | | | | FUSE file system. fuse_get_context(3) will now return the correct values. ok mpi@
* Allow write for non-regular files when file system is mounted read-only.helg2018-06-181-43/+16
| | | | | | | | Don't ask file system to check file access; always behave as if default_permissions option was specified. (this may change in a later commit) ok mpi@
* chmod(2) should return EFTYPE if the effective user ID is not thehelg2018-06-181-1/+19
| | | | | | | super-user, the mode includes the sticky bit (S_ISVTX), and path does not refer to a directory. ok mpi@
* Make callers of VOP_CREATE(9) and VOP_MKNOD(9) responsible forvisa2018-06-071-31/+13
| | | | | | unlocking the directory vnode. OK mpi@, helg@
* Pass the socket to sounlock(), this prepare the terrain for per-socketmpi2018-06-061-6/+6
| | | | | | locking. ok visa@, bluhm@
* Change wait text when waiting for FUSE file system daemon to respond.helg2018-05-231-2/+2
| | | | ok mpi@
* Implement support for libfuse use_ino option. This returns the filehelg2018-05-221-2/+2
| | | | | | | system's ino for VOP_GETATTR(9) and VOP_READDIR(9) rather than the internally generated fuse ino. ok mpi@
* The flush operation is optional so don't return ENOSYS if the FUSE file systemhelg2018-05-211-11/+13
| | | | | | doesn't implement it. ok mpi@
* Prevent race condition if file system is accessed before it ishelg2018-05-201-13/+22
| | | | | | initialised. Rather than failing, requests are now queued. ok mpi@
* Implement FBT_FLUSH. This is sent whenever a file descriptor is closed withhelg2018-05-202-39/+71
| | | | | | | | | VOP_CLOSE(9). The associated FUSE file handle is however not closed at this time and is instead closed on VOP_RELEASE(9) because that's the only time it's guaranteed to be no longer used. Directory handles are now only closed on VOP_RELEASE(9) for the same reason. ok mpi@
* Pass size argument to free(9).helg2018-05-174-10/+10
| | | | ok mpi@
* libfuse should not maintain state for FBT_READDIR. If a directory ishelg2018-05-161-2/+2
| | | | | | | | opened multiple times (either from the same process or different processes) then FUSE will not reliably return the directory entries to both file descriptors. ok mpi@
* Use memset(3) instead of bzero(3) for consistency and as per POSIXhelg2018-05-152-8/+8
| | | | recommendation.
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.