summaryrefslogtreecommitdiffstats
path: root/third_party/simplejson/README.chromium
diff options
context:
space:
mode:
authorjsbell@chromium.org <jsbell@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-10-10 23:02:39 +0000
committerjsbell@chromium.org <jsbell@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-10-10 23:02:39 +0000
commit3b95e1d0219931466d4c53da0703371f4b44faae (patch)
treecb794445e83db887fd27b5c326a65d31c5865807 /third_party/simplejson/README.chromium
parente421391b11135c0661182f9f2ff1227902a873a0 (diff)
downloadchromium_src-3b95e1d0219931466d4c53da0703371f4b44faae.zip
chromium_src-3b95e1d0219931466d4c53da0703371f4b44faae.tar.gz
chromium_src-3b95e1d0219931466d4c53da0703371f4b44faae.tar.bz2
Expose PlatformFileLock/Unlock, fix locking in Chromium's leveldb Env
The base::CreatePlatformFile() flags PLATFORM_FILE_EXCLUSIVE_READ/WRITE are ineffective on existing files on POSIX, and can't be used to implement the locking scheme required by leveldb. Add PlatformFileLock/Unlock which have the correct semantics, and use those in ChromiumEnv. Also, crib code from leveldb's env_posix.cc to handle in-process exclusivity which is not guaranteed by file locks. BUG=245471 Review URL: https://codereview.chromium.org/26306003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@228036 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party/simplejson/README.chromium')
0 files changed, 0 insertions, 0 deletions