smb_ReleaseFID cannot be called while a cm_scache_t->mx is held
shuffle the order of the smb_ReleaseFID calls so they are always after
cm_XXXRelease calls for performance.
(cherry picked from commit c484781531ce29d3d1b5c3753322be4a87dd0841)
FIXES 43332
Some sites expect single-threaded volume attaches to happen in a specific
order. The parallel attach patch also changed the attach order for sites
not specifying -vattachpar.
(cherry picked from commit e6b719a4c0a33b0b020c07c20124a40a245dbe9e)
FIXES 43551
kreltime-guard-against-null-tm-20060731 was apparently an
attempt to deal with the possibility of localtime() returning NULL by
using localtime_r instead, and zeroing the tm structure first. This has
two problems. First, localtime_r is not guaranteed to leave its output
buffer untouched or in a sane state in the event it is given invalid
input. More importantly, the second half of this delta fixed the build
on Windows (which apparently lacks localtime_r) at the expense of using
the wrong level of indirection on other platforms.
Simple is nice, but correct is important too. There is nothing wrong
with switching to localtime_r to avoid thread safety issues. However,
the correct fix for the anticipated problem was and is to check the
return value of localtime (or localtime_r), and if it is NULL, fill in
the ktime_date with suitable default values.
The attached patch does not implement the correct fix, but does fix the
double-indirection problem, so butc will again perform correctly instead
of crashing.
(cherry picked from commit e720779b7c8472a0d928b0e1429b476f073309aa)
* don't DebugBreak unless a debugger is attached
* replace afsdcell.ini with CellServDB in error message
* do not NetBIOS Reset adapters when checking to see if only the loopback
is in use because doing so breaks the existing LANA bind
* remove a deadlock in smb3.c
* do not retry dirty buffer writes when flushing in response to a suspend
* do not flush in response to a suspend when only the loopback is present
(cherry picked from commit 4f26bcfdb3c6a47d17f825e99f9d5a1bc97eba45)
fixup build dependencies for afsp_version.h
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
fixup copyrights
(cherry picked from commit 5aa0347678c472d21b99af516c64578c4af41ea9)
fixes for aix pre 5.2 (statfs64), remove a c++ style comment (makes xlc sad) and
make clean target clean
(cherry picked from commit 453abf6aa149e27622745b818afb88019e22171a)
afsp_version.h is auto-generated
====================
This delta was composed from multiple commits as part of the CVS->Git migration.
The checkin message with each commit was inconsistent.
The following are the additional commit messages.
====================
fix product version generation
(cherry picked from commit c8a86da7f76a8e71d883cda39c10251b0910302c)
Secure Endpoints Inc. is contributing its AFS plug-in for KFW 3.1's
Network Identity Manager to OpenAFS under an MIT style license.
(cherry picked from commit f72c2fc3e75a13e3736a275df35597ad43f620fa)
FIXES 42312
iafs_InactiveVCache() calls afs_InvalidateAllSegments() which says
it should be called with the vnode locked. so the lock should
probably be moved to afs_InactiveVCache() so it can be droppped
before calling afs_remunlink().
(cherry picked from commit ac52e2f3c0bec9298d020de963036409165f380e)
prevent a stack overflow if the afsd_service does not successfully
start after a request to do so is issued.
(cherry picked from commit 3c13e5f0c0423d5e724ab224af22d7d3606ef1b0)
add debugging code that can be activated with #define DEBUG_REFCOUNT
to assist in debugging scache refcount leaks
(cherry picked from commit 8919e0d5175dae85991a3782f659621c5be4056f)
reformat some code; make sure that pointers are copied while
mutexes are held; ...
(cherry picked from commit b4007635064f08d4d0f019acc9888f0d4005708c)
#ifdef DEBUG_REFCOUNT the ref count log entries so they aren't always
compiled in
comment out the remaining location where the write lock on cm_scacheLock
is dropped in order to obtain the scache mutex on the object returned
from cm_GetNewSCache(). Dropping the lock results in more than one
thread being given the same cm_scache_t which is more dangerous than
blowing away the contents of the object without holding the mutex
ensure that cm_BufWrite is always called with a non-NULL scp. Add
an assertion to double check that we do it all the time.
(cherry picked from commit ffe26eb18da581d2df02f9531d97e31e1c6dee65)
