| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
seem to be valid (vl - feel free to confirm).
Jeremy.
|
| |
|
| |
|
|
|
|
|
| |
(http://samba.org/~tridge/3_0-ctdb)
Signed-off-by: Alexander Bokovoy <ab@samba.org>
|
|
|
|
|
|
| |
locking.c:open_read_only was unused
don't export the silly boolean flag locking_init(bool read_only)
|
|
|
|
|
|
|
| |
bugs in various places whilst doing this (places that assumed
BOOL == int). I also need to fix the Samba4 pidl generation
(next checkin).
Jeremy.
|
|
|
|
| |
This removes file_id_string_static and file_id_string_static2
|
|
|
|
| |
This has been superseded by the "tdb_hashsize:<tdbname>" parameter
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Jeremy.
|
| |
|
| |
|
|
|
|
|
|
|
| |
- 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.
|
|
|
|
| |
failed expression in SMB_ASSERT.
|
|
|
|
| |
anyway.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
store the right data after cleaning lock records. This fixes
RAW-BENCH-LOCK after a recovery on a cluster
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
patch.
This changes "struct process_id" to "struct server_id", keeping both is
just too much hassle. No functional change (I hope ;-))
Volker
|
|
|
|
| |
lock_struct *
|
|
|
|
| |
Jeremy.
|
|
|
|
|
|
| |
and fix all compiler warnings in the users
metze
|
| |
|
| |
|
|
|
|
|
|
| |
Destructors now take a pointer to the "real" destroyed object as an argument.
Volker
|
| |
|
|
|
|
|
|
| |
we don't get the chainlock when getting the byte range
lock record read-only.
Jeremy.
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
| |
do with
our internal share number.
Funny that it worked at all :-)
Volker
|
|
|
|
| |
Jeremy.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Jeremy.
|
|
|
|
|
|
|
| |
requests. Maybe the Linux kernel OOM killer will
be kinder to smbd now :-). Back to tdbtorture
tests on cifsfs.
Jeremy.
|
|
|
|
|
| |
Fix a small one first.... (easy to valgrind).
Jeremy
|
|
|
|
|
|
| |
Hopefully will fix the build farm. Still a few errors
in RAW-LOCK to look at though...
Jeremy.
|
|
|
|
|
| |
cifsfs client code.
Jeremy.
|
|
|
|
|
|
|
| |
to do the upper layer directories but this is what
everyone is waiting for....
Jeremy.
|
|
|
|
|
| |
function we must copy the data before modifying.
Jeremy.
|
|
|
|
|
|
|
| |
db. Make this db self-cleaning on first read of entry after
open, and also on smbstatus -b call. Needs more testing when
I get back from Boston but passes valgrind at first look.
Jeremy.
|
|
|
|
|
| |
pass with CIFSFS.
Jeremy.
|