summaryrefslogtreecommitdiffstats
path: root/source3/smbd
Commit message (Collapse)AuthorAgeFilesLines
...
* s3: Make the write end of the echo responder pipe non-blockingVolker Lendecke2010-10-061-0/+1
| | | | | | | | Without this, we can get a writable pipe end, but the writev call on the pipe will block. Autobuild-User: Volker Lendecke <vlendec@samba.org> Autobuild-Date: Wed Oct 6 13:57:30 UTC 2010 on sn-devel-104
* Fix crash in SMB2 rename found by gentest. We must always have an lcompJeremy Allison2010-10-061-1/+1
| | | | | | | | | in the destination struct for a rename, so set the flag appropriately. Jeremy. Autobuild-User: Jeremy Allison <jra@samba.org> Autobuild-Date: Wed Oct 6 00:29:51 UTC 2010 on sn-devel-104
* s3: Stop using the write cache after an oplock breakVolker Lendecke2010-10-051-0/+1
| | | | | Autobuild-User: Volker Lendecke <vlendec@samba.org> Autobuild-Date: Tue Oct 5 10:09:38 UTC 2010 on sn-devel-104
* s3: Remove smbd_server_conn from msg_force_tdisVolker Lendecke2010-10-031-1/+7
|
* s3: Remove smbd_server_conn from process_blocking_lock_cancel_messageVolker Lendecke2010-10-031-1/+7
|
* s3: Remove smbd_server_conn from smb1 receive_unlock_msgVolker Lendecke2010-10-031-1/+9
|
* s3: Remove smbd_server_conn from msg_file_was_renamedVolker Lendecke2010-10-031-1/+8
|
* s3: Remove smbd_server_conn from validate_my_share_entriesVolker Lendecke2010-10-031-3/+5
|
* s3: Remove smbd_server_conn from msg_close_fileVolker Lendecke2010-10-031-1/+8
|
* s3: Remove smbd_server_conn from smb2 receive_unlock_msgVolker Lendecke2010-10-031-1/+9
|
* s3: Remove smbd_server_conn from process_kernel_oplock_breakVolker Lendecke2010-10-031-2/+8
|
* s3: Remove smbd_server_conn from process_oplock_break_messageVolker Lendecke2010-10-031-3/+8
|
* s3: Remove smbd_server_conn from process_oplock_async_level2_break_messageVolker Lendecke2010-10-031-2/+8
|
* s3: Lift smbd_server_conn from initial_break_processingVolker Lendecke2010-10-031-5/+9
|
* s3: Add msg_ctx_to_sconnVolker Lendecke2010-10-032-0/+15
|
* s3: I thought I had compiled this....Volker Lendecke2010-10-031-1/+1
|
* s3: Attempt to fix the IRIX buildVolker Lendecke2010-10-031-1/+1
|
* s3: Attempt to fix a ton of warnings on the build farmVolker Lendecke2010-10-031-0/+1
|
* s3: Remove talloc_autofree_context() from dmapi.cVolker Lendecke2010-10-031-2/+1
| | | | | This is a place where an explicit dmapi_destroy_session would be needed. But we don't use a destructor for this.
* s3:smbd: Increase unsupported IOCTL debug message to 2Steven Danneman2010-10-011-2/+4
| | | | | | Even printing once per connection, level 0 was too spammy with Windows clients frequently sending FSCTL_GET_OBJECT_ID which is unsupported.
* s3:events: Call all ready fd event handlers on each iteration of the main loopSteven Danneman2010-10-011-19/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, only one fd handler was being called per main message loop in all smbd child processes. In the case where multiple fds are available for reading the fd corresponding to the event closest to the beginning of the event list would be run. Obviously this is arbitrary and could cause unfairness. Usually, the first event fd is the network socket, meaning heavy load of client requests can starve out other fd events such as oplock or notify upcalls from the kernel. In this patch, I have changed the behavior of run_events() to unset any fd that it has already called a handler function, as well as decrement the number of fds that were returned from select(). This allows the caller of run_events() to iterate it, until all available fds have been handled. I then changed the main loop in smbd child processes to iterate run_events(). This way, all available fds are handled on each wake of select, while still checking for timed or signalled events between each handler function call. I also added an explicit check for EINTR from select(), which previously was masked by the fact that run_events() would handle any signal event before the return code was checked. This required a signature change to run_events() but all other callers should have no change in their behavior. I also fixed a bug in run_events() where it could be called with a selrtn value of -1, doing unecessary looping through the fd_event list when no fds were available. Also, remove the temporary echo handler hack, as all fds should be treated fairly now.
* samba: share select wrappers.Günther Deschner2010-10-011-0/+1
| | | | Guenther
* s3: Attempt to fix bug 7518Volker Lendecke2010-09-281-6/+6
| | | | | | | | | | | If select returns -1, we can't rely on the fd sets. The current code might loop endlessly because when putting an invalid fd (the closed socket?) on the read set, a select implementation might choose not to touch it but directly return with EINVAL. Thus run_events will see the socket readable, which leads to a "return true", and thus a NT_STATUS_RETRY -> same game again. We should never get into this situation, but to me the logfiles given in bug 7518 do not reveal enough information to understand how this can happen.
* s3: Increase the debuglevel for connection termination msgsVolker Lendecke2010-09-281-2/+2
|
* s3: Lift smbd_messaging_context() from open_sockets_smbd()Volker Lendecke2010-09-281-16/+14
|
* s3: Remove two calls to procid_self()Volker Lendecke2010-09-281-2/+4
|
* s3: Remove some remaining files.c globals to sconnVolker Lendecke2010-09-283-53/+49
|
* s3: Remove talloc_autofree_context() from files.cVolker Lendecke2010-09-282-6/+9
|
* s3: Lift smbd_server_conn from file_find_fdVolker Lendecke2010-09-282-4/+4
|
* s3: Remove smbd_server_conn from file_fspVolker Lendecke2010-09-281-1/+1
|
* s3: Slightly simplify file_fnumVolker Lendecke2010-09-281-2/+15
| | | | req==NULL should never happen, see the comment
* s3: Remove smbd_server_conn from file_sync_allVolker Lendecke2010-09-281-1/+1
|
* s3: Remove smbd_server_conn from file_find_subpathVolker Lendecke2010-09-281-1/+1
|
* s3: Lift smbd_server_conn from file_find_di_firstVolker Lendecke2010-09-284-8/+11
|
* s3: Lift smbd_server_conn from file_find_difVolker Lendecke2010-09-284-6/+7
|
* s3: Remove smbd_server_conn from files_forallVolker Lendecke2010-09-282-6/+6
|
* s3: Remove smbd_server_conn from file_close_userVolker Lendecke2010-09-282-3/+3
|
* s3: Remove smbd_server_conn from file_close_pidVolker Lendecke2010-09-282-3/+4
|
* s3: Remove smbd_server_conn from file_close_connVolker Lendecke2010-09-281-1/+1
|
* s3: Remove smbd_server_conn from file_new and file_freeVolker Lendecke2010-09-281-2/+2
|
* s3: Lift smbd_server_conn from file_fnumVolker Lendecke2010-09-281-4/+5
|
* s3: Move "Files" to smbd_server_connectionVolker Lendecke2010-09-283-17/+16
|
* s3: Remove "server_fd" global variableVolker Lendecke2010-09-283-9/+4
|
* Small tweak to bugfix for 7698 - Assert causes smbd to panic on invalid ↵Jeremy Allison2010-09-271-3/+3
| | | | | | | | | NetBIOS session request. Don't just fail to reply on a bad NBT name, just don't do the internal action. Jeremy.
* Change to using TDB_INCOMPATIBLE_HASH (the jenkins hash) on allJeremy Allison2010-09-271-4/+4
| | | | | | | | | | TDB_CLEAR_IF_FIRST tdb's. For tdb's like gencache where we open without CLEAR_IF_FIRST and then with CLEAR_IF_FIRST if corrupt this is still safe to use as if opening an existing tdb the new hash will be ignored - it's only used on creating a new tdb not opening an old one. Jeremy.
* s3: Make file_fnum staticVolker Lendecke2010-09-271-1/+1
|
* s3: Remove some unused codeVolker Lendecke2010-09-271-50/+0
|
* s3: Fix some commentsVolker Lendecke2010-09-271-2/+2
|
* s3: Remove talloc_autofree_context() from notify_internal_parent_init()Volker Lendecke2010-09-262-5/+4
|
* Fix bug #7698 - Assert causes smbd to panic on invalid NetBIOS session request.Jeremy Allison2010-09-262-12/+31
| | | | | | | | | | | | | | Found by the CodeNomicon test suites at the SNIA plugfest. http://www.codenomicon.com/ If an invalid NetBIOS session request is received the code in name_len() in libsmb/nmblib.c can hit an assert. Re-write name_len() and name_extract() to use "buf/len" pairs and always limit reads. Jeremy.
generated by cgit (git 2.34.1) at 2025-09-27 15:44:23 +0000