Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2009-07-10 | Remove reply_unixerror() - no longer needed. Should make Metze's refactoring ↵ | Jeremy Allison | 5 | -84/+79 | |
a lot easier. Jeremy. | |||||
2009-07-10 | s3 smb2: Remove unused variable | Tim Prouty | 1 | -1/+0 | |
2009-07-10 | s3:smbd: add support for SMB2 Lock | Stefan Metzmacher | 1 | -1/+151 | |
metze | |||||
2009-07-10 | s3:smbd: make smbd_do_locking() non static | Stefan Metzmacher | 2 | -16/+26 | |
metze | |||||
2009-07-10 | s3:smbd: abstract the main locking logic from the LockingAndX parsing | Stefan Metzmacher | 1 | -178/+254 | |
This prepares SMB2 Lock support. metze | |||||
2009-07-10 | s3:smbd: pass down the client pid to smbd_smb2_lock_send() | Stefan Metzmacher | 1 | -0/+6 | |
metze | |||||
2009-07-10 | s3:smbd: fix parsing of SMB2 Lock requests with lock_count > 1 | Stefan Metzmacher | 1 | -10/+13 | |
We should not reuse the variable 'i'. metze | |||||
2009-07-10 | s3:smbd: fix parsing of invalid SMB2 requests. | Stefan Metzmacher | 1 | -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 | |||||
2009-07-09 | s3: Fix two arguments that broke when plumbing smb_filneame through dos_mode() | Tim Prouty | 1 | -2/+2 | |
2009-07-08 | s3: Repace a char * with an smb_filename struct in reply_rmdir | Tim Prouty | 1 | -3/+8 | |
2009-07-08 | s3: Prepare open.c to switch fsp_name to an smb_filename struct | Tim Prouty | 1 | -11/+15 | |
2009-07-08 | s3 plumb smb_filename through smb_set_file_allocation_info() | Tim Prouty | 1 | -23/+12 | |
2009-07-08 | s3: Change the share_mode_lock struct to store a base_name and stream_name | Tim Prouty | 2 | -32/+56 | |
2009-07-08 | s3: Remove is_ntfs_stream_name() and split_ntfs_stream_name() | Tim Prouty | 2 | -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. | |||||
2009-07-08 | s3: Plumb smb_filename through dos_mode() and related funtions | Tim Prouty | 9 | -339/+417 | |
2009-07-08 | s3: convert unix_mode to take an smb_filename | Tim Prouty | 3 | -18/+49 | |
2009-07-08 | Rename update_stat_ex_writetime() -> update_stat_ex_mtime() | Jeremy Allison | 3 | -6/+6 | |
to better describe what we're doing here. Jeremy | |||||
2009-07-08 | The migration to struct stat_ex broke the calculation of | Jeremy Allison | 3 | -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 | |||||
2009-07-07 | s3: Migrate a few functions in open.c to take smb_filename | Tim Prouty | 1 | -13/+15 | |
2009-07-07 | s3: Remove unnecessary const qualifiers | Tim Prouty | 1 | -3/+2 | |
2009-07-07 | s3:smbd: cancel all locks that are made before the first failure | Stefan Metzmacher | 1 | -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 | |||||
2009-07-06 | s3 smb2: Fix unused variable warning | Tim Prouty | 1 | -1/+0 | |
2009-07-06 | s3: Plumb smb_filename through SMB_VFS_NTIMES | Tim Prouty | 4 | -126/+119 | |
2009-07-06 | s3 sticky write time: Removed unused args and tighten up a function by ↵ | Tim Prouty | 2 | -7/+5 | |
making an arg const | |||||
2009-07-06 | s3: Plumb smb_filename around SMB_VFS_CHFLAGS | Tim Prouty | 6 | -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. | |||||
2009-07-06 | s3: Change some filename_convert to pass in NULL for char **fname argument | Tim Prouty | 4 | -12/+11 | |
2009-07-06 | s3: Add ability to pass NULL to filename_convert for the char *fname | Tim Prouty | 1 | -7/+11 | |
The goal is to eventually remove the need for the char **fname argument once all callers have standardized on smb_filename. | |||||
2009-07-06 | s3: Plumb smb_filename through SMB_VFS_UNLINK | Tim Prouty | 4 | -160/+280 | |
2009-07-06 | s3: Plumb smb_filename through SMB_VFS_RENAME | Tim Prouty | 2 | -114/+248 | |
2009-07-03 | For non-existent streams we have to return OBJECT_NAME_NOT_FOUND | Volker Lendecke | 1 | -1/+1 | |
See the STREAMERROR s3 torture test. Jeremy, Tim, please check! | |||||
2009-07-02 | s3:smbd: add marshalling layer for SMB2 Lock support | Stefan Metzmacher | 3 | -1/+231 | |
metze | |||||
2009-07-02 | s3:smbd: add marshalling layer for SMB2 Find (QueryDirectory) support | Stefan Metzmacher | 3 | -1/+264 | |
metze | |||||
2009-07-02 | s3:smbd: add marshalling layer for SMB2 Break support (SMB 2.002 only) | Stefan Metzmacher | 3 | -1/+216 | |
metze | |||||
2009-07-02 | s3:smbd: add marshalling layer for SMB2 SetInfo support | Stefan Metzmacher | 3 | -1/+221 | |
metze | |||||
2009-07-02 | s3:smbd: add marshalling layer for SMB2 GetInfo support | Stefan Metzmacher | 3 | -1/+260 | |
metze | |||||
2009-07-02 | s3:smbd: add support for SMB2 Notify | Stefan Metzmacher | 3 | -1/+377 | |
metze | |||||
2009-07-02 | s3:smbd: make change_notify_reply() more generic and hide send_nt_replies() ↵ | Stefan Metzmacher | 2 | -14/+33 | |
behind a callback This prepares change notify support for SMB2. metze | |||||
2009-07-02 | s3:smbd: simplify the notify code a bit and always reply via ↵ | Stefan Metzmacher | 2 | -34/+27 | |
change_notify_reply() -> send_nt_replies() metze | |||||
2009-07-02 | s3:smbd: push nttrans and trans2 responses with no data to the client | Stefan Metzmacher | 2 | -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 | |||||
2009-07-02 | s3:smbd: restore the 3.0.x bahavior of send_nt_replies() | Stefan Metzmacher | 1 | -0/+5 | |
We should also set the error code, when we return no parameters or data. metze | |||||
2009-07-02 | s3:smbd: move global notify_changes_by_mid to smbd_server_connection | Stefan Metzmacher | 3 | -7/+8 | |
metze | |||||
2009-07-02 | s3:smbd: allow the offset to the path being 0 in SMB2 create | Stefan Metzmacher | 1 | -1/+3 | |
metze | |||||
2009-07-01 | Ensure we don't use delayed writes on POSIX opened files. | Jeremy Allison | 2 | -0/+15 | |
Don't remove pending writetime changes if no time changes are sent in UNIX_BASIC infolevel. Jeremy | |||||
2009-07-01 | Fix bug #6520 time stamps - e.g. last mod time is not preserved when "unix ↵ | Jeremy Allison | 1 | -3/+31 | |
extensions=yes" are set - and using latest cifs vfs client Cancel out any pending "sticky" writes or "last write" changes when doing a UNIX info level set. Jeremy. | |||||
2009-07-01 | s3:smbd: remove unused variables passed to parent_dirname() | Stefan Metzmacher | 2 | -5/+3 | |
metze | |||||
2009-06-29 | s3:fix build of old linux quota system and other unixes' quota implementation | Michael Adam | 1 | -14/+14 | |
By fixing the use of struct stat_ex. Michael | |||||
2009-06-27 | Stop listening for inotify data when there's none | Volker Lendecke | 1 | -0/+1 | |
There have been some reports that we're flooding syslog with "No data on inotify fd?!". I haven't been able to reproduce this yet. Until then, it is better to just list this message once. | |||||
2009-06-27 | Fix some nonempty blank lines | Volker Lendecke | 1 | -9/+9 | |
2009-06-27 | s3/lanman: Workaround for KB932762. | Volker Lendecke | 1 | -0/+1 | |
This addresses bug #6498. | |||||
2009-06-25 | s3: pass a valid stat into file_ntimes() | Tim Prouty | 2 | -3/+3 | |
file_ntimes() calls can_write_to_file() which expects a valid stat struct |