summaryrefslogtreecommitdiffstats
path: root/source3/modules
Commit message (Collapse)AuthorAgeFilesLines
* Add missing newlines to debug statementsSteven Danneman2009-03-251-2/+2
|
* s3 onefs: Change error status to NT_ACCESS_DENIED for errors in ↵David Kwan2009-03-241-5/+5
| | | | SET_SECURITY_DESC
* s3 OneFS: Remove usage of non-existant functionTim Prouty2009-03-231-9/+0
| | | | | The function was removed in: c16c90a1cb3b0e2ceadd3dea835a4e69acfc2fae
* Use StrCaseCmp in the dirsort moduleVolker Lendecke2009-03-221-1/+1
|
* Add dirsort moduleAndy Kelk2009-03-221-0/+194
|
* s3 onefs: Correctly error out when the read returns EOFTim Prouty2009-03-181-5/+9
| | | | Also add some more debugging.
* s3: Don't return in a void funtionTim Prouty2009-03-131-1/+1
|
* s3 OneFS: Add kernel strict locking supportDave Richards2009-03-133-10/+95
|
* s3: Add strict lock/unlock calls to the vfs layer to replace is_lockedDave Richards2009-03-132-0/+64
|
* Add a vfs_preopen module to hide fs latenciesVolker Lendecke2009-03-101-0/+456
|
* s3 OneFS: Use the public open_streams_for_deleteTim Prouty2009-03-041-113/+0
|
* Fix crashes when running RAW-ACLs against system with tdb ACL modulesJeremy Allison2009-03-042-3/+3
| | | | | (caused by the POSIX pathname fixes). Jeremy.
* Make use of gpfs_get_real_filename optionalVolker Lendecke2009-03-042-1/+10
|
* s3 OneFS: Add parameter to ignore streamsTim Prouty2009-03-034-3/+17
|
* s3 OneFS: Refactor config code and cleanup includesTim Prouty2009-03-0111-385/+453
|
* Use fsp->posix_open in preference if we have it.Jeremy Allison2009-02-252-7/+7
| | | | Jeremy.
* Ensure ACL modules work with POSIX paths.Jeremy Allison2009-02-252-22/+79
| | | | Jeremy.
* s3 OneFS: Add .snapshot directory configuration handlingTim Prouty2009-02-254-27/+201
|
* Fix use of streams modules with CIFSFS client.Jeremy Allison2009-02-252-4/+25
| | | | Jeremy.
* s3 OneFS: Fix uninitialized variableTim Prouty2009-02-241-1/+1
|
* s3: onefs_acl.c cleanupDan Sledz2009-02-241-4/+1
| | | | | Remove some duplicate code. Add a \n to a debugging statement
* S3: Add in profile counters for new vfs and syscall entries.todd stecher2009-02-244-6/+65
|
* s3 OneFS: Add a parameter that unconditionally allows execute accessTim Prouty2009-02-232-0/+26
|
* More warning fixes for Solaris.Jeremy Allison2009-02-231-4/+4
| | | | Jeremy.
* More warning fixes for Solaris.Jeremy Allison2009-02-231-4/+5
| | | | Jeremy.
* Quieten down a boatload of shadowed variable warnings on Solaris.Jeremy Allison2009-02-232-47/+47
| | | | | Makes real problems easier to spot. Jeremy.
* s3 OneFS: Add an atomic sendfile implementationTim Prouty2009-02-213-0/+282
|
* s3 OneFS: Add debugging for createfile_flagsZack Kirsch2009-02-201-12/+15
|
* s3: OneFS implementation of change notifySteven Danneman2009-02-203-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.
* Fix bug #6133 - Cannot delete non-ACL files on Solaris/ZFS/NFSv4 ACL filesystem.Jeremy Allison2009-02-201-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.
* s3 OneFS: Add shadow copy moduleTim Prouty2009-02-193-0/+1531
|
* s3 OneFS: Add file_id_create implementation to take advantage of snapshotsTim Prouty2009-02-191-0/+18
|
* s3: Add extid to the dev/inode pairTim Prouty2009-02-193-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.
* s3: Modify SMB_VFS_FILE_ID_CREATE to take a stat structTim Prouty2009-02-195-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.
* s3 OneFS: Fixes "inherit permissions" and "nt acl support" for Onefs.Zack Kirsch2009-02-191-1/+11
|
* S3: Make changes to perfcount API set for when a single request leads to ↵todd stecher2009-02-192-13/+98
| | | | | | multiple replies (e.g. reply_echo). Change test and onefs modules to match new api set (thanks Volker!).
* s3: OneFS: Pass in the client's fnum to the ifs_cbrl syscall.Zack Kirsch2009-02-181-3/+4
|
* s3: Fix OneFS bug opening streams with truncating dispositionAravind Srinivasan2009-02-181-1/+1
| | | | | Do not attempt to delete streams on a truncating open, if the name we're opening is itself a stream
* s3: Fix streams enumeration bug in OneFS implementationAravind Srinivasan2009-02-183-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().
* s3 perfcount: Fix segfault with smbclient 'echo 3 foo'Tim Prouty2009-02-161-33/+11
|
* s3 OneFS: Add defaults to the fake timestamp parametersTim Prouty2009-02-162-8/+19
|
* Replace a // style comment with a /* */ oneVolker Lendecke2009-02-141-1/+1
|
* Fix some C++ warningsVolker Lendecke2009-02-141-7/+14
|
* s3 OneFS: Add recvfile implementationTim Prouty2009-02-133-0/+198
|
* Enable total anonymization in vfs_smb_traffic_analyzer, by mapping any user ↵Holger Hetterich2009-02-131-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.
* s3 OneFS: Add vfs implementation for SMB_VFS_GET_REAL_FILE_NAMEAravind Srinivasan2009-02-131-0/+41
|
* s3: Test module for perfcount systemtodd stecher2009-02-131-0/+363
| | | | | Add 'perfcount module = pc_test' to exercise this module. Results are logged into smb.log every 50 operations (configurable via smb.conf).
* OneFS implementation of BRL VFS ops:Zack Kirsch2009-02-133-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.
* Add VFS ops for Windows BRL: Lock, Unlock and Cancel:Zack Kirsch2009-02-132-0/+114
| | | | | | | | | | | | | | | | | | | | | | | This patch adds 3 new VFS OPs for Windows byte range locking: BRL_LOCK_WINDOWS, BRL_UNLOCK_WINDOWS and BRL_CANCEL_WINDOWS. Specifically: * I renamed brl_lock_windows, brl_unlock_windows and brl_lock_cancel to *_default as the default implementations of the VFS ops. * The blocking_lock_record (BLR) is now passed into the brl_lock_windows and brl_cancel_windows paths. The Onefs implementation uses it - future implementations may find it useful too. * Created brl_lock_cancel to do what brl_lock/brl_unlock do: set up a lock_struct and call either the Posix or Windows lock function. These happen to be the same for the default implementation. * Added helper functions: increment_current_lock_count() and decrement_current_lock_count(). * Minor spelling correction in brl_timeout_fn: brl -> blr. * Changed blocking_lock_cancel() to return the BLR that it has cancelled. This allows us to assert its the lock that we wanted to cancel. If this assert ever fires, this path will need to take in the BLR to cancel, rather than choosing on its own. * Adds a small helper function: find_blocking_lock_record_by_id(). Used by the OneFS implementation, but could be useful for others.
* s3 onefs: rename custom parameter to plural to match previous usageSteven Danneman2009-02-123-5/+5
|
generated by cgit (git 2.34.1) at 2025-09-25 08:36:10 +0000