Windows: Drop Fcb Resource across SetEOF and SetAllocation
authorJeffrey Altman <jaltman@your-file-system.com>
Mon, 16 Apr 2012 19:22:35 +0000 (15:22 -0400)
committerJeffrey Altman <jaltman@secure-endpoints.com>
Tue, 17 Apr 2012 01:37:08 +0000 (18:37 -0700)
commit0ac28aa703459df60e9f18348fb1d4f73d5c042c
tree081d99841b8b74cdc12dec2a8adbaabe10a61f40
parentfd161ec0e474485c6a1a43019b802e3b663098df
Windows: Drop Fcb Resource across SetEOF and SetAllocation

If the file size or allocation is being altered, we must hold
the PagingResource and drop the Fcb Resource.  Dropping the
Fcb resource is necessary to avoid a deadlock with TrendMicro's
filter if the size is set to zero and acquiring the PagingResource
is necessary to prevent races now that the Fcb Resource is no
longer held.

Change-Id: Ie72a018adc52c479a4bb2469b2b1abe317644e8b
Reviewed-on: http://gerrit.openafs.org/7224
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Jeffrey Altman <jaltman@secure-endpoints.com>
Tested-by: Jeffrey Altman <jaltman@secure-endpoints.com>
src/WINNT/afsrdr/kernel/lib/AFSFileInfo.cpp