summaryrefslogtreecommitdiff
path: root/source3/modules/onefs.h
AgeCommit message (Collapse)AuthorFilesLines
2012-04-06build: Remove SMB_OFF_T, replace with off_tAndrew Bartlett1-2/+2
Now that we always require a 64 bit off_t, we no longer need SMB_OFF_T. Andrew Bartlett Autobuild-User: Andrew Bartlett <abartlet@samba.org> Autobuild-Date: Fri Apr 6 01:47:43 CEST 2012 on sn-devel-104
2012-04-05build: Remove SMB_STRUCT_DIR defineAndrew Bartlett1-8/+8
2012-04-05build: Remove SMB_STRUCT_DIRENT defineAndrew Bartlett1-1/+1
2011-02-23s3-proto: remove some prototypes of non-existing functions.Günther Deschner1-3/+0
Guenther Autobuild-User: Günther Deschner <gd@samba.org> Autobuild-Date: Wed Feb 23 15:42:35 CET 2011 on sn-devel-104
2010-05-18s3-secdesc: remove "typedef struct security_descriptor SEC_DESC".Günther Deschner1-4/+6
Guenther
2009-07-24s3 onefs: Fix the onefs modules after the big refactoringTim Prouty1-2/+2
2009-07-07s3 onefs: Fix a few bugs from the smb_filename migrationTim Prouty1-2/+4
2009-07-06s3: Plumb smb_filename around SMB_VFS_CHFLAGSTim Prouty1-3/+0
SMB_VFS_CHFLAGS isn't actually getting the smb_filename struct for now since it only operates on the basefile. This is the strategy for all path-based operations that will never actually operate on a stream. By clarifying the meaning of path based operations that don't take an smb_filename struct, modules that implement streams such as vfs_onefs no longer need to implement SMB_VFS_CHFLAGS to ensure it's only called on the base_name.
2009-07-06s3: Plumb smb_filename through SMB_VFS_RENAMETim Prouty1-2/+3
2009-06-25s3 onefs: Plumb smb_filename through onefs createfile pathTim Prouty1-4/+6
2009-06-15s3 onefs: Change onefs modules to use the new createfile apiTim Prouty1-4/+2
2009-05-28s3 onefs: update the onefs module to be compliant with stat_exTim Prouty1-0/+13
2009-05-12s3 onefs: Fix ignore sacl parameterTim Prouty1-2/+3
2009-03-13s3 OneFS: Add kernel strict locking supportDave Richards1-0/+8
2009-03-01s3 OneFS: Refactor config code and cleanup includesTim Prouty1-135/+1
2009-02-25s3 OneFS: Add .snapshot directory configuration handlingTim Prouty1-3/+29
2009-02-23s3 OneFS: Add a parameter that unconditionally allows execute accessTim Prouty1-0/+2
2009-02-21s3 OneFS: Add an atomic sendfile implementationTim Prouty1-0/+10
2009-02-20s3: OneFS implementation of change notifySteven Danneman1-0/+9
The OneFS Samba implementation of change notify is modeled after the usage of Linux's inotify kernel subsystem. A single call is made into the onefs.so VFS module to initialize kernel tracking of certain file change events. When these events occur a kernel notification is sent to smbd and the notification event is translated and given to the general Samba Change Notify layer through a callback function. The most difficult aspect is converting an SMB CompletionFilter to a matching ifs_event mask, and then back to an appropriate change notify action. Currently, not all possible cases are handled by the this module, but the most prevalent ones, which are tested by smbtorture, are implemented.
2009-02-18s3: Fix streams enumeration bug in OneFS implementationAravind Srinivasan1-0/+3
Previously, we didn’t call SMB_VFS_OPEN_DIR from the streams module, instead we called fdopendir(). As a result we failed to populate the dir_state list in the readdirplus module. So when we tried to view the stream data, we will always returned NULL. To solve this I separated onefs_opendir() and the initialization of the dir_state list. This is done by introducing a new utility function “onefs_rdp_add_dir_state()”, which initializes the dir_state structure and adds it to the dir_state list. This function is called from the streams module before calling readdir().
2009-02-16s3 OneFS: Add defaults to the fake timestamp parametersTim Prouty1-0/+8
2009-02-13s3 OneFS: Add recvfile implementationTim Prouty1-0/+3
2009-02-13OneFS implementation of BRL VFS ops:Zack Kirsch1-2/+17
* Much of the beginning should look familiar, as I re-used the OneFS oplock callback record concept. This was necessary to keep our own state around - it really only consists of a lock state, per asynchronous lock that is currently unsatisfied. The onefs_cbrl_callback_records map to BLRs by the id. * There are 4 states an async lock can be in. NONE means there is no async currently out for the lock, as opposed to ASYNC. DONE means we've locked *every* lock (keep in mind a request can ask for multiple locks at a time.) ERROR is an error. * onefs_cbrl_async_success: The lock_num is incremented, and the state changed, so that when process_blocking_lock_queue is run, we will try the *next* lock, rather than the same one again. * onefs_brl_lock_windows() has some complicated logic: * We do a no-op if we're passed a BLR and the matching state is ASYNC -- this means Samba is trying to get the same lock twice, and we just need to wait longer, so we return an error. * PENDING lock calls happen when the lock is being queued on the BLQ -- we do async in this case. * We also do async in the case that we're passed a BLR, but the lock is not pending. This is an async lock being probed by process_blocking_lock_queue. * We do a sync lock for any normal first request of a lock. * Failure is returned, but it doesn't go to the client unless the lock has actually timed out.
2009-02-12s3 onefs: rename custom parameter to plural to match previous usageSteven Danneman1-2/+2
2009-02-09s3: OneFS bulk directory enumeration supportSteven Danneman1-13/+33
OneFS provides the bulk directory enumeration syscall readdirplus(). This syscall has the same semantics as the NFSv3 READDIRPLUS command, returning a batch of directory entries with prefetched stat information via one syscall. This commit wraps the readdirplus() call in the existing POSIX readdir/seekdir VFS interface. By default a batch of 128 directory entries are optimistically read from the kernel into a global cache, and fed to iterative calls of VFS_OP_READDIR. The global buffers could be avoided in the future by hanging connection specific buffers off the conn struct. Added new parameter "onefs:use readdirplus" which toggles usage of this code on or off.
2009-02-09s3 OneFS: Add kernel oplocks implementationTim Prouty1-1/+1
A few functions in oplocks_onefs.c need to be accessed from the onefs vfs module. It would be ideal if oplocks were implemented at the vfs layer, but since they aren't yet, a new header is added to source3/include to make these functions available to the onefs vfs module. oplocks_onefs.o doesn't need to be linked into the onefs vfs module explicitly, since it is already linked into smbd by default.
2009-02-09s3 OneFS: Fake Timestampstodd stecher1-0/+58
This checkin enables setting arbitrary timestamps on files matching the pattern stored in smb.conf. This was a customer request for a specific workflow. Changes include: 1) configuration state machine to avoid tons of string comparisons on each and every stat. 2) Code to adjust post-stat() times to match time now, or sloptime + time now.
2009-01-23Modify OneFS module to support new NTIMES interfacestodd stecher1-0/+3
2009-01-23s3: OneFS unmappable sids support.Dan Sledz1-1/+9
Updates the onefs vfs module to add configurable behavior to deal with sids that are unknown to us. The best examples are aces that come from robocopy/xcopy. Adds the following share level options (which are specific to the vfs_onefs module): onefs: ignore unmappable sids (Default = false) If this option is set to true, sids which could not be resolved to a uid/gid are ignored. If an unmappable sid is encountered as the owner or group, the owner/group is converted to BUILTIN\Administrators. onefs: unmappable sids ignore list (Default = empty) Only the sids in the list are ignored. onefs: ignore sacls (Default = false) SACLs are ignored onefs: unmappable sids deny everyone (Default = false) If an unmappable sid is found in a deny ACE, the ACE's identity is changed to Everyone.
2009-01-11s3: Add OneFS alternate data streams implementationTim Prouty1-2/+29
2009-01-11s3: General cleanup of the open path in the OneFS vfs moduleTim Prouty1-2/+2
2008-12-09s3: Add the OneFS SMB_VFS_CREATE_FILE implementationTim Prouty1-7/+61
This is the first pass at extending the onefs vfs module to support the CIFS-specific enhancements available on OneFS. Most of this patch is massaging the sama open path to work with ifs_createfile. ifs_createfile is a CIFS-specific syscall for opening/files and directories. It adds support for: - Full in-kernel access checks using a windows access_mask - Cluster-coherent share mode locks - Cluster-coherent oplocks - Streams - Setting security descriptors at create time - Setting dos_attributes at create time This patch does not implement the samba side of the streams support or oplocks support. Tests that expect oplocks to be granted or streams to be supported will fail. This will be remedied in upcoming patches.
2008-12-02Add support for OneFS ACLsSteven Danneman1-0/+52
Add to the OneFS VFS module, support for NTFS ACLs through the calls: SMB_VFS_FGET_NT_ACL() SMB_VFS_GET_NT_ACL() SMB_VFS_FSET_NT_ACL() Also create several new onefs specific smb.conf parameters in onefs.h