summaryrefslogtreecommitdiffstats
path: root/source3/smbd
Commit message (Collapse)AuthorAgeFilesLines
...
* s3:smbd: add support for marshalling SMB2 FileFullEaInformationStefan Metzmacher2009-07-121-0/+92
| | | | metze
* s3:smbd: add support for marshalling SMB2 FileAllInformationStefan Metzmacher2009-07-121-0/+36
| | | | metze
* s3:smbd: filter out SMB2 specific private query info levels for SMB1Stefan Metzmacher2009-07-121-0/+9
| | | | metze
* s3:smbd: make smbd_do_qfilepathinfo() non static for use in SMB2Stefan Metzmacher2009-07-122-15/+31
| | | | metze
* s3:smbd: split calculation and mashalling of file index and access_maskStefan Metzmacher2009-07-121-13/+19
| | | | metze
* s3:smbd: split out smbd_do_qfilepathinfo() from call_trans2qfilepathinfo()Stefan Metzmacher2009-07-121-459/+504
| | | | | | This prepares SMB2 GetInfo. metze
* s3:smbd: add missing return after reply_nterror()Stefan Metzmacher2009-07-121-0/+1
| | | | metze
* Remove reply_unixerror() - no longer needed. Should make Metze's refactoring ↵Jeremy Allison2009-07-105-84/+79
| | | | | | a lot easier. Jeremy.
* s3 smb2: Remove unused variableTim Prouty2009-07-101-1/+0
|
* s3:smbd: add support for SMB2 LockStefan Metzmacher2009-07-101-1/+151
| | | | metze
* s3:smbd: make smbd_do_locking() non staticStefan Metzmacher2009-07-102-16/+26
| | | | metze
* s3:smbd: abstract the main locking logic from the LockingAndX parsingStefan Metzmacher2009-07-101-178/+254
| | | | | | This prepares SMB2 Lock support. metze
* s3:smbd: pass down the client pid to smbd_smb2_lock_send()Stefan Metzmacher2009-07-101-0/+6
| | | | metze
* s3:smbd: fix parsing of SMB2 Lock requests with lock_count > 1Stefan Metzmacher2009-07-101-10/+13
| | | | | | We should not reuse the variable 'i'. metze
* s3:smbd: fix parsing of invalid SMB2 requests.Stefan Metzmacher2009-07-101-2/+2
| | | | | | | | | | Because of 0 - 2 => 0xFFFFFFFE, we got EMSGSIZE from the tstream layer. And terminate the transport connection. Instead we should let the caller deal with the invalid parameter, when checking the body size. So the caller always gets at least a 2 byte body. metze
* s3: Fix two arguments that broke when plumbing smb_filneame through dos_mode()Tim Prouty2009-07-091-2/+2
|
* s3: Repace a char * with an smb_filename struct in reply_rmdirTim Prouty2009-07-081-3/+8
|
* s3: Prepare open.c to switch fsp_name to an smb_filename structTim Prouty2009-07-081-11/+15
|
* s3 plumb smb_filename through smb_set_file_allocation_info()Tim Prouty2009-07-081-23/+12
|
* s3: Change the share_mode_lock struct to store a base_name and stream_nameTim Prouty2009-07-082-32/+56
|
* s3: Remove is_ntfs_stream_name() and split_ntfs_stream_name()Tim Prouty2009-07-082-49/+3
| | | | | 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-089-339/+417
|
* s3: convert unix_mode to take an smb_filenameTim Prouty2009-07-083-18/+49
|
* Rename update_stat_ex_writetime() -> update_stat_ex_mtime()Jeremy Allison2009-07-083-6/+6
| | | | | to better describe what we're doing here. Jeremy
* The migration to struct stat_ex broke the calculation ofJeremy Allison2009-07-083-10/+57
| | | | | | | | | | | | | | | | create time from the existing timestamps (for systems that need to do this). Once the write time is changed via a sticky write, the create time might need to be recalculated. To do this I needed to add a bool into struct stat_ex to remember if the st_ex_btime field was calculated, or read from the OS. Also fixed the returning of modified write timestamps in the return from NTCreateX, SMBattr and SMBattrE (which weren't taking into account the modified timestamp stored in the open file table). Attempting to fix an issue with Excel 2003 and offline files. Volker and Metze, please review. Jeremy
* s3: Migrate a few functions in open.c to take smb_filenameTim Prouty2009-07-071-13/+15
|
* s3: Remove unnecessary const qualifiersTim Prouty2009-07-071-3/+2
|
* s3:smbd: cancel all locks that are made before the first failureStefan Metzmacher2009-07-071-6/+6
| | | | | | | | s3:smbd: cancel all locks that are made before the first failure We never reached the cleanup code and directly returned the error. metze
* s3 smb2: Fix unused variable warningTim Prouty2009-07-061-1/+0
|
* s3: Plumb smb_filename through SMB_VFS_NTIMESTim Prouty2009-07-064-126/+119
|
* s3 sticky write time: Removed unused args and tighten up a function by ↵Tim Prouty2009-07-062-7/+5
| | | | making an arg const
* s3: Plumb smb_filename around SMB_VFS_CHFLAGSTim Prouty2009-07-066-99/+115
| | | | | | | | | | | 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: Change some filename_convert to pass in NULL for char **fname argumentTim Prouty2009-07-064-12/+11
|
* s3: Add ability to pass NULL to filename_convert for the char *fnameTim Prouty2009-07-061-7/+11
| | | | | The goal is to eventually remove the need for the char **fname argument once all callers have standardized on smb_filename.
* s3: Plumb smb_filename through SMB_VFS_UNLINKTim Prouty2009-07-064-160/+280
|
* s3: Plumb smb_filename through SMB_VFS_RENAMETim Prouty2009-07-062-114/+248
|
* For non-existent streams we have to return OBJECT_NAME_NOT_FOUNDVolker Lendecke2009-07-031-1/+1
| | | | | | See the STREAMERROR s3 torture test. Jeremy, Tim, please check!
* s3:smbd: add marshalling layer for SMB2 Lock supportStefan Metzmacher2009-07-023-1/+231
| | | | metze
* s3:smbd: add marshalling layer for SMB2 Find (QueryDirectory) supportStefan Metzmacher2009-07-023-1/+264
| | | | metze
* s3:smbd: add marshalling layer for SMB2 Break support (SMB 2.002 only)Stefan Metzmacher2009-07-023-1/+216
| | | | metze
* s3:smbd: add marshalling layer for SMB2 SetInfo supportStefan Metzmacher2009-07-023-1/+221
| | | | metze
* s3:smbd: add marshalling layer for SMB2 GetInfo supportStefan Metzmacher2009-07-023-1/+260
| | | | metze
* s3:smbd: add support for SMB2 NotifyStefan Metzmacher2009-07-023-1/+377
| | | | metze
* s3:smbd: make change_notify_reply() more generic and hide send_nt_replies() ↵Stefan Metzmacher2009-07-022-14/+33
| | | | | | | | behind a callback This prepares change notify support for SMB2. metze
* s3:smbd: simplify the notify code a bit and always reply via ↵Stefan Metzmacher2009-07-022-34/+27
| | | | | | change_notify_reply() -> send_nt_replies() metze
* s3:smbd: push nttrans and trans2 responses with no data to the clientStefan Metzmacher2009-07-022-0/+16
| | | | | | | | | | For sync replies it's not a problem, as construct_reply() will send the response, but for async replies we would not send the reply to the client. Currently the notify code works arround this manually, so I assume we didn't have a bug here. But the next commits will simplify the notify code. metze
* s3:smbd: restore the 3.0.x bahavior of send_nt_replies()Stefan Metzmacher2009-07-021-0/+5
| | | | | | We should also set the error code, when we return no parameters or data. metze
* s3:smbd: move global notify_changes_by_mid to smbd_server_connectionStefan Metzmacher2009-07-023-7/+8
| | | | metze
* s3:smbd: allow the offset to the path being 0 in SMB2 createStefan Metzmacher2009-07-021-1/+3
| | | | metze
* Ensure we don't use delayed writes on POSIX opened files.Jeremy Allison2009-07-012-0/+15
| | | | | | Don't remove pending writetime changes if no time changes are sent in UNIX_BASIC infolevel. Jeremy
generated by cgit (git 2.34.1) at 2025-10-01 07:25:17 +0000