summaryrefslogtreecommitdiffstats
path: root/source3/modules
Commit message (Collapse)AuthorAgeFilesLines
...
* Add "store create time" parameter (docs to follow)Jeremy Allison2009-08-121-0/+9
| | | | | that stores the create time in the user.DosTimestamps EA. Jeremy.
* Fix some warnings in the AIX ACL code.Jeremy Allison2009-08-121-4/+3
| | | | Jeremy.
* Move the checks for null timestamps down below the VFS_NTIMESJeremy Allison2009-08-071-0/+15
| | | | | | layer (as it's done in onefs). This simplifies greatly the code in smb_set_file_time() w.r.t. changenotify messages. Jeremy.
* Fix breakage for connect function after API change (connect -> connect_fn)Alexander Bokovoy2009-08-022-2/+2
|
* s3: Attempt to fix hpuxacl moduleTim Prouty2009-07-292-5/+13
|
* shadow_copy2: The system getrealfilename() can't deal with a 0-length fnameVolker Lendecke2009-07-291-0/+3
| | | | | | This fixes viewing the content of snapshots in the share root directory. We have to treat the filename that *just* consists of "@GMT-YYYY.MM.DD-HH.MM.SS" like the share root, which is the current working directory.
* Fix the build breakage by #including modules/vfs_acl_common.cJeremy Allison2009-07-273-21/+31
| | | | | | | into acl_tdb and acl_xattr. Duplicates the code size, but keeps the code in common so I don't have to do bug fixes in two places (which is what I really cared about). Jeremy.
* Cleanup patch after "new VFS"Volker Lendecke2009-07-251-1/+1
|
* Cleanup patch after "struct stat_ex"Volker Lendecke2009-07-251-2/+2
|
* s3 onefs: Fix the onefs modules after the big refactoringTim Prouty2009-07-244-10/+10
|
* Factor out common code into vfs_acl_common.c.Jeremy Allison2009-07-243-1272/+653
| | | | Jeremy.
* Make acl_tdb match acl_xattr. Large duplication ofJeremy Allison2009-07-241-68/+225
| | | | | code here needs tidying up. Compiles but not yet tested. Jeremy.
* Fix hash function in acl_xattr to be SHA256, makeJeremy Allison2009-07-242-62/+100
| | | | | | | | the hash function selectable. Upgrade version. Compiles but not fully tested yet (coming). Make vfs_acl_tdb.c compile - this needs updating to match acl_xattr (also coming soon). Jeremy.
* Move the "enum _vfs_op_type" to full_auditVolker Lendecke2009-07-241-0/+142
| | | | | It's only used there now. Someone should now go in and simplify full_audit... :-)
* Make the smbd VFS typesafeVolker Lendecke2009-07-2443-1587/+710
|
* Some more VFS type errorsVolker Lendecke2009-07-241-2/+2
|
* Fix some C++ warningsVolker Lendecke2009-07-241-4/+7
|
* s3: Remove unnecessary callers of get_full_smb_filenameTim Prouty2009-07-211-40/+18
| | | | | | | This often times means explicitly denying certain operations on a stream as they are not supported or don't make sense at a particular level. At some point in the future these can be enabled, but for now it's better to remove ambiguity
* s3: Finish plumbing the fsp->fsp_name smb_fname conversion through the modules.Tim Prouty2009-07-2021-252/+300
|
* Fix a few type errors in VFS modulesVolker Lendecke2009-07-196-10/+18
|
* reject ACLs with DESC_DACL_PROTECTED on GPFSChristian Ambach2009-07-141-0/+5
| | | | | | | | as GPFS does not support the ACE4_FLAG_NO_PROPAGATE NFSv4 flag (which would be the mapping for the DESC_DACL_PROTECTED flag), the status of this flag is currently silently ignored by Samba. That means that if you deselect the "Allow inheritable permissions..." checkbox in Windows' ACL dialog and then apply the ACL, the flag will be back immediately. To make sure that automatic migration with e.g. robocopy does not lead to ACLs silently (and unintentionally) changed, this patch adds an explicit check for this flag and if set, it will return NT_STATUS_NOT_SUPPORTED so errors are shown up on the Windows side and the Administrator is aware of the ACLs not being settable like intended Signed-off-by: Christian Ambach <christian.ambach@de.ibm.com>
* Add hash values to the xattr ACLS to determine whenJeremy Allison2009-07-101-55/+158
| | | | | | | | an underlying POSIX ACL is changed out from under us. Passes RAW-ACL test up to "invalid owner" problem when trying to create a file owned by Everyone. Now needs porting to modules/vfs_acl_tdb.c Jeremy.
* s3: Prepare open.c to switch fsp_name to an smb_filename structTim Prouty2009-07-081-12/+15
|
* s3: Change the share_mode_lock struct to store a base_name and stream_nameTim Prouty2009-07-081-15/+7
|
* s3: Remove is_ntfs_stream_name() and split_ntfs_stream_name()Tim Prouty2009-07-082-57/+12
| | | | | Actually I moved split_ntfs_stream_name into torture.c which is the one consumer of it. This could probably be changed at some point.
* s3: Plumb smb_filename through dos_mode() and related funtionsTim Prouty2009-07-082-3/+12
|
* s3: convert unix_mode to take an smb_filenameTim Prouty2009-07-082-5/+16
|
* s3 onefs: Fix a few bugs from the smb_filename migrationTim Prouty2009-07-073-49/+35
|
* Attempt to fix the build of vfs_catia.c -- Tim, please check!Volker Lendecke2009-07-071-2/+2
|
* s3: Update streaminfo implementations now that only base names are passed ↵Tim Prouty2009-07-064-21/+20
| | | | through the vfs
* s3 audit: Fix a memory leakTim Prouty2009-07-061-4/+4
|
* s3: Plumb smb_filename through SMB_VFS_NTIMESTim Prouty2009-07-068-39/+91
|
* s3 catia: Remove pointless VOPs from catiaTim Prouty2009-07-061-84/+0
|
* s3: Plumb smb_filename around SMB_VFS_CHFLAGSTim Prouty2009-07-063-25/+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.
* s3: Plumb smb_filename through SMB_VFS_UNLINKTim Prouty2009-07-0616-213/+370
|
* s3 audit: Remove some recently introduced memory leaks in the audit modulesTim Prouty2009-07-062-12/+45
|
* s3 audit: Remove the usesless static function declarations from the audit ↵Tim Prouty2009-07-063-641/+308
| | | | modules
* s3 onefs: Fix failure in POSIX smbtorture testTim Prouty2009-07-061-2/+2
| | | | | | The return value of readlink was a bool instead of an int, which caused the length of the returned value to never be >1.
* s3: Plumb smb_filename through SMB_VFS_RENAMETim Prouty2009-07-0615-202/+355
|
* do not merge ACEs with different SMB_ACE4_INHERIT_ONLY_ACE flag, this leads ↵Christian Ambach2009-07-061-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to wrong inheritance flags in the ACL e.g. (on GPFS) user:10000036:rwxc:allow (X)READ/LIST (X)WRITE/CREATE (X)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED (X)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED user:10000036:rwxc:allow:FileInherit:DirInherit:InheritOnly (X)READ/LIST (X)WRITE/CREATE (X)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED (X)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED group:10000005:rwxc:allow (X)READ/LIST (X)WRITE/CREATE (X)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED (X)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED group:10000005:rwxc:allow:FileInherit:DirInherit:InheritOnly (X)READ/LIST (X)WRITE/CREATE (X)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED (X)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED would be merged to user:10000036:rwxc:allow:FileInherit:DirInherit:InheritOnly (X)READ/LIST (X)WRITE/CREATE (X)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED (X)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED group:10000005:rwxc:allow:FileInherit:DirInherit:InheritOnly (X)READ/LIST (X)WRITE/CREATE (X)MKDIR (X)SYNCHRONIZE (X)READ_ACL (X)READ_ATTR (X)READ_NAMED (X)DELETE (X)DELETE_CHILD (X)CHOWN (X)EXEC/SEARCH (X)WRITE_ACL (X)WRITE_ATTR (X)WRITE_NAMED so the explicit right for the user on the parent directory will be gone (the InheritOnly flag only accounts to subdirectories) thus leaving the user without access to the directory itself Signed-off-by: Christian Ambach <christian.ambach@de.ibm.com>
* s3:onefs_open: remove unused variable passed to parent_dirname()Stefan Metzmacher2009-07-011-2/+1
| | | | metze
* s3 onefs: Plumb smb_filename through onefs createfile pathTim Prouty2009-06-254-221/+322
|
* Add a \n to a debug message in smbacl4_nfs42winVolker Lendecke2009-06-251-1/+1
|
* s3: Plumb smb_filename through SMB_VFS_STAT and SMB_VFS_LSTATTim Prouty2009-06-2417-255/+524
| | | | | | | | | | | | | This patch introduces two new temporary helper functions vfs_stat_smb_fname and vfs_lstat_smb_fname. They basically allowed me to call the new smb_filename version of stat, while avoiding plumbing it through callers that are still too inconvenient. As the conversion moves along, I will be able to remove callers of this, with the goal being to remove all callers. There was also a bug in create_synthetic_smb_fname_split (also a temporary utility function) that caused it to incorrectly handle filenames with ':'s in them when in posix mode. This is now fixed.
* s3 onefs: Remove dfs resolution from create_file() now that it's being done ↵Tim Prouty2009-06-171-22/+1
| | | | at a higher level
* s3: Change SMB_VFS_OPEN to take an smb_filename structTim Prouty2009-06-1717-117/+352
| | | | | | | | | | | | This was a little messy because of all of the vfs modules I had to touch. Most of them were pretty straight forward, but the streams modules required a little attention to handle smb_filename. Since the use of smb_filename enables the vfs modules to access the raw, over-the-wire stream, a little bit of the handling that was being done by split_ntfs_stream_name has now been shifted into the individual stream modules. It may be a little more code, but overall it gives more flexibility to the streams modules, while also allowing correct stream handling.
* s3: Plumb smb_filename from create_file all of the way down to fd_openTim Prouty2009-06-171-7/+2
| | | | | | | | | | | | I used the smb_filename struct everywhere that was feasible for the first pass. There are still some places in this path that need to be changed to use smb_filename, but this is a good start. I also: - Removed fname/path arguments from a few functions that weren't really using them. - Added a utility function for detecting whether an smb_filename is a stream.
* s3 onefs: Fix reading over the end of the array, because the incorrect array ↵Tim Prouty2009-06-151-2/+3
| | | | was being read.
* s3 onefs: Change onefs modules to use the new createfile apiTim Prouty2009-06-153-43/+46
|
* s3: Plumb smb_filename through SMB_VFS_CREATE_FILETim Prouty2009-06-122-21/+13
|
generated by cgit (git 2.34.1) at 2026-03-06 10:40:39 +0000