summaryrefslogtreecommitdiffstats
path: root/source/locking
Commit message (Collapse)AuthorAgeFilesLines
* [GLUE] Rsync SAMBA_3_0 SVN r25598 in order to create the v3-0-test branch.samba-misc-tags/initial-v3-0-testGerald (Jerry) Carter2007-10-103-461/+354
|
* r23759: Fix make test -- sorryVolker Lendecke2007-10-101-2/+2
|
* r23755: Fix Coverity id 384Volker Lendecke2007-10-101-1/+7
|
* r23516: Fix bug found & fixed by Doug Rudoff (doug_rudoff@isilon.com)Jeremy Allison2007-10-101-0/+6
| | | | | | | - when cleaning up invalid locks make sure we mark the lck struct as modified so it'll get saved back correctly (that was the original intent). Jeremy.
* r23510: Tidy calls to smb_panic by removing trailing newlines. Print theJames Peach2007-10-103-28/+28
| | | | failed expression in SMB_ASSERT.
* r23486: Ok, this time with a hopefully successful make test in the right place:Volker Lendecke2007-10-101-4/+0
| | | | Remove two local variables
* r23316: Ouch... This would not have run in production without cluster codeVolker Lendecke2007-10-101-2/+2
| | | | anyway.
* r23222: share_mode_forall() is only for counting and status display stuff, soVolker Lendecke2007-10-101-1/+1
| | | | traverse_read is enough here
* r23204: Add MSG_SMB_BRL_VALIDATE. Tridge, this is a bit different from your bzrVolker Lendecke2007-10-101-0/+106
| | | | | | | | | | branch, please check if it fulfils your needs. Two changes: The validation is not done inside the brlock.c traverse_fn, it's done as a separate routine. Secondly, this patch does not call the checker routines in smbcontrol directly but depends on a running smbd.
* r23195: Add void *private_data to brl_forallVolker Lendecke2007-10-101-10/+28
|
* r23183: Check in a change made by Tridge:Volker Lendecke2007-10-103-80/+52
| | | | | | | | | | | | | This replaces the internal explicit dev/ino file id representation by a "struct file_id". This is necessary as cluster file systems and NFS don't necessarily assign the same device number to the shared file system. With this structure in place we can now easily add different schemes to map a file to a unique 64-bit device node. Jeremy, you might note that I did not change the external interface of smb_share_modes.c. Volker
* r23169: Merge 535 of Tridge's bzr tree:Volker Lendecke2007-10-101-2/+5
| | | | | store the right data after cleaning lock records. This fixes RAW-BENCH-LOCK after a recovery on a cluster
* r23165: Convert brlock.tdb to dbwrapVolker Lendecke2007-10-101-38/+51
|
* r23164: Minor cosmetic checkinVolker Lendecke2007-10-101-2/+2
|
* r23163: Convert locking.tdb to dbwrapVolker Lendecke2007-10-101-91/+109
|
* r23162: Make use of messaging_send_bufVolker Lendecke2007-10-101-4/+2
|
* r23100: Implement the delete on close semantics I've just tested forJeremy Allison2007-10-101-1/+45
| | | | | | in Samba4 smbtorture. Fix rename on an open file handle. Needed for 3.0.25a. Jeremy.
* r23096: Make the lock failure message prettier.James Peach2007-10-101-4/+4
|
* r23014: For all branches, ensure that if we're blocked on a POSIXJeremy Allison2007-10-102-5/+26
| | | | | | | | lock we know nothing about that we retry the lock every 10 seconds instead of waiting for the standard select timeout. This is how we used to (and are supposed to) work. Jeremy.
* r22846: Chunk one to replace message_send_pid with messaging_send: Deep insideVolker Lendecke2007-10-102-32/+45
| | | | | | locking/locking.c we have to send retry messages to timed lock holders. The majority of this patch passes a "struct messaging_context" down there. No functional change, survives make test.
* r22736: Start to merge the low-hanging fruit from the now 7000-line cluster ↵Volker Lendecke2007-10-101-6/+6
| | | | | | | | | patch. This changes "struct process_id" to "struct server_id", keeping both is just too much hassle. No functional change (I hope ;-)) Volker
* r22688: Change lock_data in struct byte_range_lock from void * to struct ↵Volker Lendecke2007-10-101-24/+15
| | | | lock_struct *
* r22588: Make all uses of TALLOC_MEMDUP consistent.Jeremy Allison2007-10-101-3/+8
| | | | Jeremy.
* r22542: Move over to using the _strict varients of the tallocJeremy Allison2007-10-101-1/+1
| | | | | calls. No functional changes. Looks bigger than it is :-). Jeremy.
* r22009: change TDB_DATA from char * to unsigned char *Stefan Metzmacher2007-10-103-18/+18
| | | | | | and fix all compiler warnings in the users metze
* r21726: Fix stupid cut-n-paste typo. Thanks to volker forJeremy Allison2007-10-101-1/+1
| | | | | being on the ball..... :-). Jeremy.
* r21724: Optimization pointed out by Volker. If we don'tJeremy Allison2007-10-101-0/+20
| | | | | | have any outstanding locks or blocking locks then we don't need to read the lock db. on close. Jeremy.
* r21723: Make use of the per-hashchain "freelists"Volker Lendecke2007-10-102-0/+6
|
* r21706: get_delete_on_close_flag() is the perfect candidate for ↵Volker Lendecke2007-10-101-7/+21
| | | | tdb_parse_record()
* r21257: Better fix for bug #4188 :Jeremy Allison2007-10-101-36/+1
| | | | | | Windows Vista RC1 and RC2 can't delete directory on Samba share based on work by Joe Meadows <jmeadows@webopolis.com>. Jeremy.
* r21191: Add in the POSIX open/mkdir/unlink calls.Jeremy Allison2007-10-102-8/+15
| | | | | | | | Move more error code returns to NTSTATUS. Client test code to follow... See if this passes the build-farm before I add it into 3.0.25. Jeremy.
* r20916: Add in the delete on close final fix - but only enabledJeremy Allison2007-10-101-0/+4
| | | | | with -DDEVELOPER. Jeremy.
* r20883: W00t! I now understand how "delete on close" reallyJeremy Allison2007-10-101-23/+16
| | | | | | | | | | | | | | | | works - even with the strange "initial delete on close" semantics. The "initial delete on close" flag isn't committed to the share mode db until the handle is closed, and is discarded if any real "delete on close" was set. This allows me to remove the "initial_delete_on_close" flag from the share db, and move it into a BOOL in files_struct. Warning ! You must do a make clean after this. Cope with the wrinkle in directory delete on close which is done differently from files. We now pass all Samba4 smbtortute BASE-DELETE tests except for the one checking that files can't be created in a directory which has the delete on close set (possibly expensive to fix). Jeremy.
* r20873: Some correctness fixes w.r.t. Samba4 torture BASE-DELETE.Jeremy Allison2007-10-101-0/+40
| | | | | | | | Allow us to correctly refuse to set delete on close on a non-empty directory. There are still some delete-on-close wrinkles to be fixed, but I understand how to do that better now. I'll fix this tomorrow. Jeremy.
* r19668: Convert the locking params to use struct share_param instead of snumVolker Lendecke2007-10-103-17/+16
|
* r19078: talloc_strdup can failVolker Lendecke2007-10-101-0/+6
|
* r17924: Get rid of warnings now that talloc is merged.Volker Lendecke2007-10-102-6/+2
| | | | | | Destructors now take a pointer to the "real" destroyed object as an argument. Volker
* r17452: Some C++ warningsVolker Lendecke2007-10-102-3/+4
|
* r17346: Add optimisation vl needs for the cluster code whereJeremy Allison2007-10-102-11/+40
| | | | | | we don't get the chainlock when getting the byte range lock record read-only. Jeremy.
* r17314: Optimisation for POSIX locking. If we're downgradingJeremy Allison2007-10-102-31/+70
| | | | | | | a POSIX lock (applying a read-lock) and we overlap pending read locks then send them an unlock message, we may have allowed them to proceed. Jeremy.
* r17293: After the results from the cluster tests in Germany,Jeremy Allison2007-10-102-8/+0
| | | | | | | | | | | | | | | | | | | | | | | | fix the messaging code to call the efficient calls : save_re_uid() set_effective_uid(0); messaging_op restore_re_uid(); instead of using heavyweight become_root()/unbecome_root() pairs around all messaging code. Fixup the messaging code to ensure sec_init() is called (only once) so that non-root processes still work when sending messages. This is a lighter weight solution to become_root()/unbecome_root() (which swaps all the supplemental groups) and should be more efficient. I will migrate all server code over to using this (a similar technique should be used in the passdb backend where needed). Jeremy.
* r17279: conn->cnum is the tid we've given to the client. This has nothing to ↵Volker Lendecke2007-10-101-6/+6
| | | | | | | | | | do with our internal share number. Funny that it worked at all :-) Volker
* r17276: Don't change the POSIX lock ref count if posix locking = no.Jeremy Allison2007-10-101-2/+2
| | | | Jeremy.
* r17181: Fix the build farm RAW-READ bug. When making a copyJeremy Allison2007-10-101-1/+3
| | | | | | | | | | of the lock array in order to delete them individually it's also important to make a copy of the *size* of this array. Otherwise the unlock decrements the termination index of your for loop :-). Doh ! Big thanks to Volker for showing me how to set up the build farm to track this one down. This is not a 3.0.23a issue. Jeremy.
* r17177: Get rid of a global variable by adding a private data pointer toVolker Lendecke2007-10-101-5/+22
| | | | | | share_mode_forall(). Volker
* r17105: Fix the race Volker found - we had a non-lockedJeremy Allison2007-10-102-17/+19
| | | | | | | | | | | | | | | | | | | | | region between detecting a pending lock was needed and when we added the blocking lock record. Make sure that we hold the lock over all this period. Removed the old code for doing blocking locks on SMB requests that never block (the old SMBlock and friends). Discovered something interesting about the strange NT_STATUS_FILE_LOCK_CONFLICT return. If we asked for a lock with zero timeout, and we got an error of NT_STATUS_FILE_LOCK_CONFLICT, treat it as though it was a blocking lock with a timeout of 150 - 300ms. This only happens when timeout is sent as zero and can be seen quite clearly in ethereal. This is the real replacement for old do_lock_spin() code. Re-worked the blocking lock select timeout to correctly use milliseconds instead of the old second level resolution (far too coarse for this work). Jeremy.
* r17098: Samba3 now cleanly passes Samba4 RAW-LOCK tortureJeremy Allison2007-10-102-89/+70
| | | | | | | | test. Phew - that was painful :-). But what it means is that we now implement lock cancels and I can add lock cancels into POSIX lock handling which will fix the fast/slow system call issue with cifsfs ! Jeremy.
* r17046: Ensure we're using the right pointers ...Jeremy Allison2007-10-101-11/+7
| | | | Jeremy.
* r17043: Fix memleak when processing CIFS POSIX lock/unlockJeremy Allison2007-10-101-4/+5
| | | | | | | requests. Maybe the Linux kernel OOM killer will be kinder to smbd now :-). Back to tdbtorture tests on cifsfs. Jeremy.
* r17041: Trying to track down a *big* memory leak in the new lock code.Jeremy Allison2007-10-102-1/+2
| | | | | Fix a small one first.... (easy to valgrind). Jeremy
generated by cgit (git 2.34.1) at 2025-08-28 21:15:07 +0000