summaryrefslogtreecommitdiff
path: root/source3/modules
AgeCommit message (Collapse)AuthorFilesLines
2009-03-27Fix the build of nfsv4_acls.cVolker Lendecke1-1/+1
.. after adding smb_iconv_convenience to ndr_size_security_descriptor()
2009-03-26Try and fix the build farm RAW-STREAMS errors. Ordering ofJeremy Allison1-2/+2
modules shouldn't matter, so as vfs_streams_depot doesn't implement get/setxattrs then call into the full VFS stack at the top. Jeremy
2009-03-25Add missing newlines to debug statementsSteven Danneman1-2/+2
2009-03-24s3 onefs: Change error status to NT_ACCESS_DENIED for errors in ↵David Kwan1-5/+5
SET_SECURITY_DESC
2009-03-23s3 OneFS: Remove usage of non-existant functionTim Prouty1-9/+0
The function was removed in: c16c90a1cb3b0e2ceadd3dea835a4e69acfc2fae
2009-03-22Use StrCaseCmp in the dirsort moduleVolker Lendecke1-1/+1
2009-03-22Add dirsort moduleAndy Kelk1-0/+194
2009-03-18s3 onefs: Correctly error out when the read returns EOFTim Prouty1-5/+9
Also add some more debugging.
2009-03-13s3: Don't return in a void funtionTim Prouty1-1/+1
2009-03-13s3 OneFS: Add kernel strict locking supportDave Richards3-10/+95
2009-03-13s3: Add strict lock/unlock calls to the vfs layer to replace is_lockedDave Richards2-0/+64
2009-03-10Add a vfs_preopen module to hide fs latenciesVolker Lendecke1-0/+456
2009-03-04s3 OneFS: Use the public open_streams_for_deleteTim Prouty1-113/+0
2009-03-04Fix crashes when running RAW-ACLs against system with tdb ACL modulesJeremy Allison2-3/+3
(caused by the POSIX pathname fixes). Jeremy.
2009-03-04Make use of gpfs_get_real_filename optionalVolker Lendecke2-1/+10
2009-03-03s3 OneFS: Add parameter to ignore streamsTim Prouty4-3/+17
2009-03-01s3 OneFS: Refactor config code and cleanup includesTim Prouty11-385/+453
2009-02-25Use fsp->posix_open in preference if we have it.Jeremy Allison2-7/+7
Jeremy.
2009-02-25Ensure ACL modules work with POSIX paths.Jeremy Allison2-22/+79
Jeremy.
2009-02-25s3 OneFS: Add .snapshot directory configuration handlingTim Prouty4-27/+201
2009-02-25Fix use of streams modules with CIFSFS client.Jeremy Allison2-4/+25
Jeremy.
2009-02-24s3 OneFS: Fix uninitialized variableTim Prouty1-1/+1
2009-02-24s3: onefs_acl.c cleanupDan Sledz1-4/+1
Remove some duplicate code. Add a \n to a debugging statement
2009-02-24S3: Add in profile counters for new vfs and syscall entries.todd stecher4-6/+65
2009-02-23s3 OneFS: Add a parameter that unconditionally allows execute accessTim Prouty2-0/+26
2009-02-23More warning fixes for Solaris.Jeremy Allison1-4/+4
Jeremy.
2009-02-23More warning fixes for Solaris.Jeremy Allison1-4/+5
Jeremy.
2009-02-23Quieten down a boatload of shadowed variable warnings on Solaris.Jeremy Allison2-47/+47
Makes real problems easier to spot. Jeremy.
2009-02-21s3 OneFS: Add an atomic sendfile implementationTim Prouty3-0/+282
2009-02-20s3 OneFS: Add debugging for createfile_flagsZack Kirsch1-12/+15
2009-02-20s3: OneFS implementation of change notifySteven Danneman3-0/+691
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-20Fix bug #6133 - Cannot delete non-ACL files on Solaris/ZFS/NFSv4 ACL filesystem.Jeremy Allison1-1/+7
As the NFSv4 ACL mapping code doesn't map write directory into the DELETE_CHILD permission bit (which we require before allowing a delete) no one can delete files without an explicit DELETE_CHILD bit set on the directory. Add this mapping. Jeremy.
2009-02-19s3 OneFS: Add shadow copy moduleTim Prouty3-0/+1531
2009-02-19s3 OneFS: Add file_id_create implementation to take advantage of snapshotsTim Prouty1-0/+18
2009-02-19s3: Add extid to the dev/inode pairTim Prouty3-0/+10
This extends the file_id struct to add an additional generic uint64_t field: extid. For backwards compatibility with dev/inodes stored in xattr_tdbs and acl_tdbs, the ext id is ignored for these databases. This patch should cause no functional change on systems that don't use SMB_VFS_FILE_ID_CREATE to set the extid. Existing code that uses the smb_share_mode library will need to be updated to be compatibile with the new extid.
2009-02-19s3: Modify SMB_VFS_FILE_ID_CREATE to take a stat structTim Prouty5-20/+29
Since file_id_create_dev is incompatible with the concept of file_ids, it is now static and in the one file that needs it.
2009-02-19s3 OneFS: Fixes "inherit permissions" and "nt acl support" for Onefs.Zack Kirsch1-1/+11
2009-02-19S3: Make changes to perfcount API set for when a single request leads to ↵todd stecher2-13/+98
multiple replies (e.g. reply_echo). Change test and onefs modules to match new api set (thanks Volker!).
2009-02-18s3: OneFS: Pass in the client's fnum to the ifs_cbrl syscall.Zack Kirsch1-3/+4
2009-02-18s3: Fix OneFS bug opening streams with truncating dispositionAravind Srinivasan1-1/+1
Do not attempt to delete streams on a truncating open, if the name we're opening is itself a stream
2009-02-18s3: Fix streams enumeration bug in OneFS implementationAravind Srinivasan3-18/+68
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 perfcount: Fix segfault with smbclient 'echo 3 foo'Tim Prouty1-33/+11
2009-02-16s3 OneFS: Add defaults to the fake timestamp parametersTim Prouty2-8/+19
2009-02-14Replace a // style comment with a /* */ oneVolker Lendecke1-1/+1
2009-02-14Fix some C++ warningsVolker Lendecke1-7/+14
2009-02-13s3 OneFS: Add recvfile implementationTim Prouty3-0/+198
2009-02-13Enable total anonymization in vfs_smb_traffic_analyzer, by mapping any user ↵Holger Hetterich1-5/+16
names to the one given by anonymize_prefix, without generating a hash number. This setting is optional and is compatible with the module configuration format of Samba 3.3.
2009-02-13s3 OneFS: Add vfs implementation for SMB_VFS_GET_REAL_FILE_NAMEAravind Srinivasan1-0/+41
2009-02-13s3: Test module for perfcount systemtodd stecher1-0/+363
Add 'perfcount module = pc_test' to exercise this module. Results are logged into smb.log every 50 operations (configurable via smb.conf).
2009-02-13OneFS implementation of BRL VFS ops:Zack Kirsch3-2/+476
* 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.
generated by cgit (git 2.34.1) at 2024-11-01 04:44:41 +0000